# CVE-2026-0988: Glib: glib: denial of service via integer overflow in g_buffered_input_stream_peek()

> An integer overflow in Glib's buffered input stream allows attackers to cause application crashes via crafted input, resulting in denial of service.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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:** 21 Jan 2026
- **Updated:** 24 Apr 2026
- **Also known as:** AZL-75017, AZL-75020, BELL-CVE-2026-0988, DEBIAN-CVE-2026-0988, ECHO-28c4-b486-37b4, GHSA-m2x7-c9gp-xc46, OESA-2026-1291, OESA-2026-1293, OESA-2026-1294, SUSE-SU-2026:0264-1, SUSE-SU-2026:0266-1, SUSE-SU-2026:0286-1, SUSE-SU-2026:0458-1, UBUNTU-CVE-2026-0988, USN-7971-1, openSUSE-SU-2026:10089-1

## What is CVE-2026-0988?

CVE-2026-0988 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Jan 2026. 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. Missing validation of offset and count parameters in the g_buffered_input_stream_peek() function can lead to an integer overflow during length calculation. When specially crafted values are provided, this overflow results in an incorrect size being passed to memcpy(), triggering a buffer overflow. This can cause application crashes, leading to a Denial of Service (DoS).

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glib2` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.62.6-150200.3.39.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.78.6-150600.4.28.1 |
| `glib2` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.48.2-12.55.1 |
| `glib2` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 2.70.5-150400.3.34.1 |
| `glib2` | openSUSE:Leap 15.6 | All versions | 2.78.6-150600.4.28.1 |
| `glib2-doc` | openSUSE:Leap 15.6 | All versions | 2.78.6-150600.4.28.1 |
| `glib2` | openSUSE:Tumbleweed | All versions | 2.86.3-2.1 |

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

Apply the vendor's patch.

## Is CVE-2026-0988 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0988 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Jan 2026. 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-2026-0988 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-0988/ (Markdown: https://insights.sbomify.com/CVE-2026-0988/index.md)
```

## Sources

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

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