cve.bz

CVE-2026-92542 Authentication Bypass by Spoofing

6.9 mediumEPSS 0.07%

Medium (6.9). EPSS 0.07% estimated probability of exploitation activity in the next 30 days.

On this page
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

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.07% (unchanged from 0.07% a week ago; 0.07% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-290 Authentication Bypass by Spoofing
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-92542 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92542?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92542?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92542 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • docker:docker engine
  • docker:docker engine overlay network driver
  • moby:moby overlay network driver

Versions

From the CNA's record in the CVE List.

ProductAffected
Docker Enginebefore 25.0.19
Docker Enginefrom 26.0.0 before 29.8.2
Docker Engine overlay network driverbefore v25.0.19
Docker Engine overlay network driverv26.0.0 and later
Moby overlay network driverfrom v2.0.0-beta.0 before v2.0.0-beta.25

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14docker.iono fix listedDEBIAN-CVE-2026-92542
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 moredocker.io, docker.io-appno fix listedUBUNTU-CVE-2026-92542
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-92542
Alpinev3.24docker29.8.2-r0ALPINE-CVE-2026-92542
Azure Linux3moby-engineno fix listedAZL-107739
Alpaquitastreamdocker29.8.2-r0BELL-CVE-2026-92542

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat has evaluated this vulnerability as having an Important severity rather than Moderate because an authenticated local user can craft datagrams to bypass network boundaries and compromise integrity or availability across encrypted container segments without requiring administrative privileges. However, Red Hat container ecosystems such as OpenShift and standard enterprise host configurations deploy Podman and Kubernetes runtimes rather than Docker Swarm. Because Swarm mode and its encrypted overlay network drivers are not used or enabled by default in supported Red Hat platforms, standard deployments are not exposed to this flaw.

ProductPackageStateAdvisory
Multicluster Engine for Kubernetesmulticluster-engine/assisted-service-9-rhel9Affected
Multicluster Global Hubmulticluster-globalhub/multicluster-globalhub-grafana-rhel9Will not fix
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/acm-grafana-rhel9Not affected
Red Hat Ceph Storage 5rhceph/rhceph-5-dashboard-rhel8Affected
Red Hat Ceph Storage 7rhceph/grafana-rhel9Affected
Red Hat Ceph Storage 9rhceph/grafana-rhel10Affected
Red Hat Enterprise Linux 10grafanaNot affected
Red Hat Enterprise Linux 9grafanaNot affected
Red Hat OpenShift Container Platform 4openshift4/ose-agent-installer-api-server-rhel8Not affected
Red Hat OpenShift Container Platform 4openshift4/ose-agent-installer-api-server-rhel9Affected
Red Hat OpenShift Container Platform 4openshift4/ose-consoleNot affected
Red Hat OpenShift Container Platform 5openshift5/ose-agent-installer-api-server-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92542.

Attack patterns (CAPEC)

  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
  • CAPEC-473 Signature Spoof
  • CAPEC-476 Signature Spoofing by Misrepresentation Likelihood: Low · Severity: High
  • CAPEC-667 Bluetooth Impersonation AttackS (BIAS) Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON