CVE-2026-120830: Red Hat Enterprise Linux 10 · Out-of-bounds Read
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 3 Nov 2026, 00:58 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 7.4 |
|---|
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10libslirp | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8container-tools:rhel8/libslirp | Affected– | Fixed in– |
| Red Hat Enterprise Linux 9libslirp | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4libslirp | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8 | Affected– | Fixed in– |
| Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9 | Affected– | Fixed in– |
AI-suggested
Red Hat currently does not have a practical temporary workaround that fully mitigates this issue while meeting usability and stability standards. Customers should apply the relevant security updates from Red Hat when they become available. Monitoring Red Hat's advisory page for updates is recommended.
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.