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

> An integer overflow in GLib's base64 encoder allows out-of-bounds writes, potentially leading to code execution or crashes when processing large inputs.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jan 2026
- **Updated:** 2 Jun 2026
- **Also known as:** AZL-75467, AZL-75920, BELL-CVE-2026-1484, DEBIAN-CVE-2026-1484, ECHO-5566-e5f1-09d5, GHSA-r2rp-r5cj-6c6x, UBUNTU-CVE-2026-1484

## What is CVE-2026-1484?

CVE-2026-1484 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-1484?


## How do I fix CVE-2026-1484?

Apply the vendor's patch.

## Is CVE-2026-1484 being exploited?

There is no known exploitation of CVE-2026-1484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1484 and fix it if it is affected.

What it is: CVE-2026-1484 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1484 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1484/ (Markdown: https://insights.sbomify.com/CVE-2026-1484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1484
- OSV: https://osv.dev/vulnerability/CVE-2026-1484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1484/
Summaries are generated and may contain mistakes; the official description above is the record.