# CVE-2026-95520: Integer overflow in Red Hat Enterprise Linux 10

> An integer overflow in RPM parsing allows heap-based buffer overflow and potential code execution when processing malicious packages.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** AZL-105813, DEBIAN-CVE-2026-95520, ECHO-2188-9e89-f630, GHSA-4hhr-mf67-g46r, UBUNTU-CVE-2026-95520

## What is CVE-2026-95520?

CVE-2026-95520 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A heap-based buffer overflow flaw was found in rpm. Parsing a symlink entry in an untrusted RPM package whose declared RPMTAG_LONGFILESIZES value is 0xFFFFFFFFFFFFFFFF causes an integer overflow in iterReadArchiveNext() that shrinks a buffer allocation to one byte, after which the payload's independently-controlled cpio filesize field is used to write attacker-controlled data past the end of that allocation. This is reachable via rpm2cpio, rpm2archive, and rpm -qlvp on an  untrusted package.

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

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


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

No fix has been published for CVE-2026-95520 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95520 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-95520 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-95520/ (Markdown: https://insights.sbomify.com/CVE-2026-95520/index.md)
```

## Sources

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

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