CVE Tools
Track your stack

CVE-2026-92542

Blind VXLAN injection into encrypted overlay networks from cluster peer

No known exploitation. EPSS puts it in the 0th percentile. Fixed versions are out.

CVSS —Not scoredEPSS percentile0th<0.1% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix3 products4 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Docker EngineAffected: < 25.0.19Upgrade to: 25.0.19Affected: ≥ 26.0.0, < 29.8.2Upgrade to: 29.8.2Stated by: CVE record
  • Docker Engine overlay network driverAffected: < v25.0.19Upgrade to: v25.0.19Affected: v26.0.0Upgrade to: not statedStated by: CVE record
  • Moby overlay network driverAffected: ≥ v2.0.0-beta.0, < v2.0.0-beta.25Upgrade to: v2.0.0-beta.25Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS0th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

<0.1% chance of exploitation activity in the next 30 days, which ranks it in the 0th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 1 day, from the signal feeds we watch.

  1. Workaround availablerecord updated
  2. Workaround availableworkaround available, published, weakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Docker Engine, not every advisory.