cve.bz

CVE-2026-76654 kubernetes kubernetes: Link Following

5.8 mediumEPSS 0.4%

Medium (5.8) in kubernetes kubernetes. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 37th 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-11-03. 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-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-76654 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-76654?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-76654?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-76654 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

Versions

From the CNA's record in the CVE List.

ProductAffected
Kubernetesfrom v1.34.0 through v1.34.11
Kubernetesfrom v1.35.0 through v1.35.8
Kubernetesfrom v1.36.0 through v1.36.4
Kubernetesfrom v1.37.0 through v1.37.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux3kubernetesno fix listedAZL-111137

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Only Windows workers are in scope. WMCO is what ships and installs kubelet.exe on those nodes. The Linux kubelet used on control plane and RHCOS workers does not include the vulnerable Windows path.

Red Hat's mitigation

Clusters with no Windows nodes need no change.

These steps reduce exposure:

- Limit who can create pods that schedule onto Windows nodes.

- Prevent Windows nodes from opening SMB/UNC connections to untrusted networks.

ProductPackageStateAdvisory
Red Hat OpenShift for Windows Containersopenshift4-wincw/windows-machine-config-operator-bundleFix deferred
Red Hat OpenShift for Windows Containersopenshift4-wincw/windows-machine-config-rhel9-operatorAffected

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-76654.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

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

References

Check your stackJSON