# CVE-2025-14087: Glib: glib: buffer underflow in gvariant parser leads to heap corruption

> Remote attackers can trigger heap corruption via malicious input in the GVariant parser, potentially causing denial of service or code execution.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2025
- **Updated:** 14 Oct 2026
- **Also known as:** AZL-72283, AZL-72296, BELL-CVE-2025-14087, CLSA-2026-1771412328, CLSA-2026-1771412927, CLSA-2026-1771579997, CLSA-2026-1771580716, CLSA-2026-1771854105, CLSA-2026-1771854372, CLSA-2026-1771854684, CLSA-2026-1771855171, CLSA-2026-1771857296, CLSA-2026-1771857466, CLSA-2026-1772110471, DEBIAN-CVE-2025-14087, ECHO-b0a6-cdfd-d774, GHSA-frh9-7wfp-w73p, JLSEC-2026-488, MINI-ch54-wrx5-g9rh, RHSA-2026:19566, UBUNTU-CVE-2025-14087

## What is CVE-2025-14087?

CVE-2025-14087 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in GLib (Gnome Lib). This vulnerability allows a remote attacker to cause heap corruption, leading to a denial of service or potential code execution via a buffer-underflow in the GVariant parser when processing maliciously crafted input strings.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-14087?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glib2` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |
| `glib2-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |
| `glib2-devel` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |
| `glib2-doc` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |
| `glib2-fam` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |
| `glib2-static` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |
| `glib2-tests` | Red Hat:rhel_els:7 | All versions | 0:2.56.1-12.el7_9 |

Products: Gnome Glib, Redhat Enterprise Linux.

## How do I fix CVE-2025-14087?

Apply the vendor's patch.

## Is CVE-2025-14087 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2020-35457](https://insights.sbomify.com/CVE-2020-35457/): Integer overflow in n/a (high 7.8)
- [CVE-2009-3289](https://insights.sbomify.com/CVE-2009-3289/): Privilege escalation in n/a (high 7.8)
- [CVE-2025-13601](https://insights.sbomify.com/CVE-2025-13601/): Glib: integer overflow in in g_escape_uri_string() (high 7.7)
- [CVE-2026-58016](https://insights.sbomify.com/CVE-2026-58016/): Glib: integer underflow in gio/gdbusintrospection.c via "g_dbus_node_info_new_for_xml" (high 7.5)
- [CVE-2025-4056](https://insights.sbomify.com/CVE-2025-4056/): Glib: glib crash after long command line (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14087 and fix it if it is affected.

What it is: CVE-2025-14087 is a medium-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14087 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-2025-14087/ (Markdown: https://insights.sbomify.com/CVE-2025-14087/index.md)
```

## Sources

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

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