CVE-2026-1484 | Glib: integer overflow leading to buffer underflow and out-of-bounds write in glib g_base64_encode()

A flaw was found in the GLib Base64 encoding routine when processing very large input data. Due to incorrect use of integer types during length calculation, the library may miscalculate buffer boundaries. This can cause memory writes outside the allocated buffer. Applications that process untrusted or extremely large Base64 input using GLib may crash or behave unpredictably.

Published: 2026-01-27 Last update: 2026-06-02 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-1484 is rated Low Risk (18.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-1484

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-21 0.07% 0.02% -0.05%
2 2026-02-24 0.03% 0.07% +0.03%
3 2026-01-28 — 0.03% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-1484

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.2 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.6 2.5 [email protected]

Weakness enumeration for CVE-2026-1484

GitHub Security Advisory for CVE-2026-1484

GHSA-r2rp-r5cj-6c6x · Severity: medium — A flaw was found in the GLib Base64 encoding routine when processing very large input data. Due...

OS Trackers for CVE-2026-1484

vendor priority summary link
debian not yet assigned CVE-2026-1484 not yet assigned priority: Debian including 1 source packages (glib2.0), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-1484
redhat medium — https://access.redhat.com/security/cve/CVE-2026-1484
suse high CVE-2026-1484 severity important: SUSE including 400 source package names (13.2-9.67:coreutils-9.4-5.1, 13.2-9.67:libglib-2_0-0-2.76.2-12.1, …), 1348 product×package rows across 166 product lines (Container suse/manager/5.0/x86_64/proxy-httpd, Container suse/manager/5.0/x86_64/proxy-salt-broker, … (166 product lines)): Fixed 1100, Known Affected 231, First Fixed 17. https://www.suse.com/security/cve/CVE-2026-1484/
ubuntu medium CVE-2026-1484 medium priority: Ubuntu including 1 source packages (glib2.0), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needed 4, released 4. https://ubuntu.com/security/CVE-2026-1484

Affected software / configurations for CVE-2026-1484

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-1484

cvelogic Threat Intelligence