Live › vulnerability › CVE-2026-115449
Go to dashboardlibslirp, the user-mode networking library used by QEMU and similar tools, mishandles ICMP echo replies when the normal ICMP socket is unavailable. A reply length mismatch leaks the host's real IP address to the guest, breaking NAT isolation.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems that run guests on user-mode (SLIRP) networking through libslirp, such as QEMU guests using the default user networking backend, are the exposed case. Hosts that use bridged, tap or other non-SLIRP networking, or that do not run libslirp-based guests, can skip it. The sources do not say which libslirp versions are fixed.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in libslirp. When handling ICMP echo requests, the reply length is not updated to match the actual data received from the host. Under specific conditions where the normal ICMP socket is unavailable, this length mismatch causes the host's real IP address to be leaked to the guest in the echo reply, breaking the NAT isolation that user-mode networking is expected to provide.
This page as .md · .json · in your agent: get_signal("CVE-2026-115449")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.