LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25741: Symlink Exchange Can Allow Host Filesystem Access

A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-25741 is a Kubernetes flaw where a user able to create a container with subPath volume mounts could reach files outside the intended volume, including host filesystem data. For businesses, the concern is tenant or workload isolation failure inside affected clusters.

Executive priority

Treat as high priority for shared, multi-tenant, or CI-driven Kubernetes environments. Prioritize confirming affected cluster versions and applying vendor guidance because successful abuse could undermine node-level file isolation.

Technical view

Kubernetes subPath volume mount handling could be bypassed through a symlink exchange, allowing access outside the mounted volume. The CVSS 3.1 score is 8.8 high, with low complexity, low privileges required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to Kubernetes clusters where users, service accounts, CI systems, or tenants can create or modify Pods using subPath volume mounts. The source bundle does not specify affected version ranges.

Exploitation context

The bundle does not cite active exploitation, and KEV status is false. Exploitation requires some Kubernetes privilege to create a container, but no user interaction is indicated by the CVSS vector.

Researcher notes

Evidence supports a Kubernetes subPath symlink exchange issue with host filesystem access impact. The provided bundle lacks exact fixed versions, affected version ranges, proof of exploitation, and detailed mitigations, so remediation should defer to the Kubernetes advisory and vendor notices.

Mitigation direction

  • Review Kubernetes advisory and GitHub issue for fixed version guidance.
  • Upgrade Kubernetes components according to vendor-published remediation instructions.
  • Inventory workloads using subPath volume mounts.
  • Restrict who can create or modify Pods in affected clusters.
  • Check downstream vendor advisories, including NetApp if applicable.

Validation and detection

  • Identify clusters and distributions potentially covered by the Kubernetes advisory.
  • Search workload manifests for subPath volume mount usage.
  • Review RBAC for principals allowed to create or update Pods.
  • Confirm remediation against the Kubernetes security announcement and issue.
  • Check host access monitoring for unexpected volume boundary violations.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25741 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-25741Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KubernetesKubernetesunspecified, unspecified, unspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.