Vulnerability DatabaseCVE-2026-115539

CVE-2026-115539: 
Docker vulnerability analysis and mitigation

Overview

CVE-2026-115539 is a privilege escalation vulnerability in SwarmKit's Cluster-API proxy, where the proxy can overwrite a forwarded client's TLS identity with an intermediary manager's identity. The root cause is that WithMetadataForwardTLSInfo replaces outgoing metadata with a copy of the incoming metadata, discarding the redirect guard's changes when built with grpc-go 1.39 or later. Affected software includes github.com/moby/swarmkit/v2 before version 2.1.3, github.com/docker/docker at version 23.0.0 and later, github.com/moby/moby/v2 up to and including v2.0.0-beta.28, and github.com/moby/swarmkit at version 1.12.1-0.20220307221335-616e8db4c3b0. The vulnerability was published on November 10, 2026, and carries a CVSS v4.0 base score of 7.7 (High) (GitHub Advisory, ENISA EUVD).

Technical details

The vulnerability is classified as CWE-441 (Unintended Proxy or Intermediary / 'Confused Deputy'). The defect originates from a behavioral change introduced in grpc-go v1.39, which changed metadata.FromIncomingContext and metadata.NewOutgoingContext to return copies rather than live references. Prior to grpc-go v1.39, the WithMetadataForwardTLSInfo and redirectChecker middlewares composed correctly by accident — both operated on the same underlying metadata map. After grpc-go v1.39, WithMetadataForwardTLSInfo's call to metadata.FromIncomingContext returns the pristine incoming context, and its subsequent call to metadata.NewOutgoingContext clobbers any changes the redirect guard (redirectChecker) had made to the outgoing metadata, rendering the redirect checker inert. During a short window after a Swarm leader change, two proxy hops through managers with inconsistent views of the leader can be chained to exploit this defect, allowing an attacker with a valid worker node TLS certificate and private key to obtain a manager node certificate for their own key (GitHub Advisory).

Impact

Successful exploitation allows an attacker holding a valid worker node TLS certificate and private key to escalate privileges to manager level within a Docker Swarm cluster by obtaining a valid manager node TLS certificate for their own key. This privilege escalation grants the attacker full control over the Swarm cluster, including the ability to deploy, modify, or destroy services and access sensitive cluster configuration and secrets. The CVSS v4.0 scoring reflects high impacts to confidentiality, integrity, and availability of the vulnerable system (GitHub Advisory).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the time of publication. The EPSS score is 0.0, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires the attacker to already possess a valid worker node TLS certificate and private key, and to time the attack during the short window following a Swarm leader change — conditions that limit opportunistic exploitation but remain realistic for an insider or a compromised worker node (GitHub Advisory, ENISA EUVD).

Exploitation steps

  1. Obtain worker credentials: Acquire a valid TLS certificate and private key for a worker node in the target Docker Swarm cluster (e.g., via compromise of an existing worker node).
  2. Monitor for leader change: Observe the Swarm cluster for a leader election event, which opens a short window during which managers may have inconsistent views of the current leader.
  3. Initiate proxy hop chain: Using the worker node credentials, send a Cluster-API request that is proxied through a first manager node that still believes the old leader is authoritative.
  4. Exploit metadata clobbering: The first manager proxy hop forwards the request; due to the WithMetadataForwardTLSInfo defect, the outgoing metadata (including redirect guard changes) is overwritten with the incoming metadata, stripping the identity-preservation guard.
  5. Second proxy hop: The request is forwarded through a second manager with an inconsistent view of the leader, completing the two-hop chain that bypasses the redirect checker.
  6. Obtain manager certificate: The Cluster-API issues a manager node TLS certificate for the attacker's own key, escalating the attacker's privileges from worker to manager within the Swarm cluster (GitHub Advisory).

Indicators of compromise

  • Network: Unexpected Cluster-API certificate issuance requests originating from worker nodes, particularly during or shortly after a Swarm leader election event; unusual gRPC traffic patterns involving multiple proxy hops between manager nodes.
  • Logs: Swarm manager logs showing certificate signing requests (CSRs) from worker node identities resulting in manager-role certificates being issued; log entries reflecting leader election events coinciding with certificate issuance activity.
  • File System / Certificates: Presence of manager-level TLS certificates associated with keys that were previously only used for worker node authentication; unexpected certificate files on nodes that should only hold worker credentials.
  • Process / Cluster State: Worker nodes appearing in the Swarm cluster with manager-level roles or permissions that were not explicitly granted by an administrator (GitHub Advisory).

Mitigation and workarounds

The fixed version for github.com/moby/swarmkit/v2 is 2.1.3; users should upgrade to this version or later. For github.com/docker/docker (version 23.0.0 and later) and github.com/moby/moby/v2 (up to v2.0.0-beta.28), no patched versions are listed in the advisory at time of publication — users should monitor the upstream repositories for fixes. As a general workaround, restricting network access to Swarm manager APIs and minimizing the number of worker nodes with access to valid TLS credentials can reduce the attack surface. Organizations should also monitor for unexpected leader election events and certificate issuance activity (GitHub Advisory).

Community reactions

The advisory was published by thaJeztah on the moby/swarmkit GitHub repository on November 10, 2026, with credit to abdulraheemalick as the finder. No significant broader media coverage, researcher commentary, or social media discussion has been identified beyond the initial advisory and automated vulnerability database entries (GitHub Advisory).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Ubuntu

Unknown

bionic (esm-apps)

docker.io

Unknown

devel

docker.io

Unknown

focal (esm-apps)

docker.io

Unknown

jammy

docker.io

Unknown

jammy (esm-apps)

docker.io

Unknown

noble

docker.io

Unknown

noble (esm-apps)

docker.io

Unknown

resolute

docker.io

Unknown

Alpine

Fixed

edge

docker: 29.9.3-r0

Fixed

Source: This report was generated using AI

Related Docker vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-115539HIGH7.7
  • Docker logoDocker
  • docker.io
NoYesNov 10, 2026
CVE-2026-115538HIGH7
  • Docker logoDocker
  • github.com/moby/moby/v2
NoYesNov 10, 2026
CVE-2026-97054MEDIUM5.9
  • Go logoGo
  • rhc-worker-playbook
NoYesNov 11, 2026
CVE-2026-121520MEDIUM4.5
  • Docker logoDocker
  • podmansh
NoNoNov 03, 2026
CVE-2026-121542LOW1.8
  • Docker logoDocker
  • docker-buildx
NoNoNov 03, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management