Skip to content
statance
MenuClose
high · CVSS 7.4

CVE-2026-95508

Libslirp: libslirp: heap buffer overflow in dhcpv6/tftp response builders on small interface mtu

Published 22 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 02:52 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
libslirpRed HatDefault status: affectedSee vendor advisory
container-tools:rhel8/libslirpRed HatDefault status: affectedSee vendor advisory
libslirpRed HatDefault status: affectedSee vendor advisory
libslirpRed HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-8Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed