CVE-2026-92542GHSA-6M9P-4H64-M6VH
Blind VXLAN injection into encrypted overlay networks from cluster peer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 25.0.19, 29.8.2, v25.0.19, v2.0.0-beta.25
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN datagrams sent from the kernel and forged datagrams sent by user processes. Any packet sent from the host network namespace of a Linux Swarm node is encrypted with the overlay-network IPsec parameters which meets the following criteria: • UDP datagram • Destination port is the Swarm data-path port • Datagram starts with a VXLAN header for the VNI of an encrypted overlay network which any running container on the node is connected to
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Docker Docker Engine
fixed in 25.0.19; From 26.0.0 · fixed in 29.8.2
- github.com/docker/docker/libnetwork/drivers/overlay
fixed in v25.0.19; From v26.0.0 · fixed in *
- github.com/moby/moby/v2/daemon/libnetwork/drivers/overlay
From v2.0.0-beta.0 · fixed in v2.0.0-beta.25