Kubernetes up to 1.34.11/1.35.8/1.36.4/1.37.0 kubelet subPath link following

Summaryinfo

A vulnerability identified as problematic has been detected in Kubernetes up to 1.34.11/1.35.8/1.36.4/1.37.0. This affects an unknown function of the component kubelet. The manipulation of the argument subPath leads to link following. This vulnerability is referenced as CVE-2026-76654. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Kubernetes up to 1.34.11/1.35.8/1.36.4/1.37.0. It has been rated as problematic. This issue affects some unknown functionality of the component kubelet. The manipulation of the argument subPath with an unknown input leads to a link following vulnerability. Using CWE to declare the problem leads to CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. Impacted is confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-76654 since 08/19/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/26/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Virtualization Software

Name

• Kubernetes

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.34.0
• 1.34.1
• 1.34.2
• 1.34.3
• 1.34.4
• 1.34.5
• 1.34.6
• 1.34.7
• 1.34.8
• 1.34.9
• 1.34.10
• 1.34.11
• 1.35
• 1.35.0
• 1.35.1
• 1.35.2
• 1.35.3
• 1.35.4
• 1.35.5
• 1.35.6
• 1.35.7
• 1.35.8
• 1.36
• 1.36.0
• 1.36.1
• 1.36.2
• 1.36.3
• 1.36.4
• 1.37.0

License

• open-source

Website

• Product: https://github.com/kubernetes/kubernetes/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion