# CVE-2026-95508: Libslirp: libslirp: heap buffer overflow in dhcpv6/tftp response builders on small interface mtu

> Heap buffer overflow in libslirp allows guest-triggered DoS or code execution on hosts with small MTU settings.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** AZL-103472, DEBIAN-CVE-2026-95508, GHSA-3qjr-gg7g-qcrr, UBUNTU-CVE-2026-95508

## What is CVE-2026-95508?

CVE-2026-95508 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap-based buffer overflow was found in the DHCPv6 and TFTP response builders of libslirp. When the host is configured with a small interface MTU, a guest-supplied DHCPv6 CLIENTID option or TFTP blksize option can overflow the reply buffer with attacker-controlled content and length, resulting in denial of service and potentially arbitrary code execution in the host process. The default interface MTU is not affected.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-95508 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95508 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 22 Sep 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-95508 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-95508/ (Markdown: https://insights.sbomify.com/CVE-2026-95508/index.md)
```

## Sources

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

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