CVE-2026-76654

Subpath symlinking on Windows nodes permits NTLM coercion

  • Medium 5.8

Description

An NTLM coercion vulnerability exists on Windows nodes when the subPath supplied in a pod's volumeMounts is set to a symbolic link that points to an attacker-controlled network share. When a kubelet resolves symlinks, it does not reject a target that resolves to a UNC path. As a result, the kubelet will transparently attempt to authenticate to the share using NTLM. This allows an attacker to obtain the NetNTLMv2 hash of the account under which the kubelet is running. An attacker could then attempt to crack the hash to retrieve the corresponding password or relay it to impersonate the node, if the node is domain-joined.

Key facts

Published
26 Oct 2026
Last changed
3 Nov 2026
Assigned by
kubernetes
EPSS
0.427% likely to be exploited in the next 30 days, higher than 37.478% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.8CVSS 3.1, Mediumfrom the CNA (kubernetes)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N

What to do

  • To mitigate this vulnerability, upgrade Kubernetes: https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/CNA solution statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-132 Symlink Attack (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
KubernetesKubernetes
  • Default status: unaffected
  • v1.34.0 up to and including v1.34.11 (affected)
  • v1.35.0 up to and including v1.35.8 (affected)
  • v1.36.0 up to and including v1.36.4 (affected)
  • v1.37.0 up to and including v1.37.0 (affected)

Timeline

  1. 26 Oct 2026 Published

Weakness

References