CVE-2026-120830

Libslirp: libslirp: out-of-bounds heap read in icmp_forward_error() leading to information disclosure

  • High 7.4

Description

A flaw was found in libslirp in icmp_forward_error(). When building an ICMP error response, the length of the quoted original IPv4 packet was taken from the IP header without clamping it to the actual buffer length. A truncated or malformed packet could cause an out-of-bounds heap read, leaking host memory into the ICMP error packet returned to a guest or container.

Key facts

Published
3 Nov 2026
Last changed
9 Nov 2026
Assigned by
redhat
EPSS
0.221% likely to be exploited in the next 30 days, higher than 12.818% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.4CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

What to do

  • Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when/if they become available. --- CME Mitigation Guidance (2026-11-04) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to clamp quoted IPv4 payload length to actual buffer bounds in libslirp icmp_forward_error before copying data into ICMP error responses: upgrade to the corresponding fixed Red Hat builds, which clamp s_ip_len to the source buffer length msrc->m_len before copying payload data into the ICMP error packet, closing crafted truncated IPv4 packets with ip_len exceeding mbuf length. Until patched, this is a concern on guests or containers transmitting network traffic through libslirp, so restrict untrusted guests or containers from transmitting network traffic across libslirp virtual network interfaces. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds heap read defect — apply the upstream patch to fully remediate.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected

Timeline

  1. 10 Oct 2026 Reported to Red Hat.
  2. 30 Oct 2026 Made public.
  3. 3 Nov 2026 Published

Weakness

References