cve.bz

CVE-2026-103435 anthropic @anthropic-ai/claude-code: Path traversal

7.7 highEPSS 0.3%

High (7.7) in anthropic @anthropic-ai/claude-code. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Claude Code validated that a target file path resided within the project working directory at permission-check time, but re-resolved the path at write time without repeating that validation. This time-of-check to time-of-use (TOCTOU) gap allowed an attacker who could write to the workspace to atomically replace a project file with a symlink, causing Claude Code to follow the symlink and write its output to an arbitrary file outside the project sandbox. Exploitation required the ability to win a race condition against the write operation and write access to the shared workspace, enabling a lower-privileged attacker to redirect benign edits to sensitive files (e.g., shell configuration) in a higher-privileged session. Users on standard Claude Code auto-update have received this fix already. Users performing manual updates are advised to update to the latest version. Thank you to hackerone.com/c_h4ck_0 for reporting this issue.

Severity

CVSS 4.0

7.7 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th 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: total, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-61 UNIX Symbolic Link (Symlink) Following
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
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-103435 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103435?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103435?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-103435 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

  • anthropic:@anthropic-ai/claude-code

Versions

From the CNA's record in the CVE List.

ProductAffected
Anthropic @anthropic-ai/claude-codebefore 2.1.129

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in Claude Code (claude-code), which is bundled in the Red Hat OpenShift Dev Spaces plugin registry container image (devspaces/pluginregistry-rhel9) in the 3.28, 3.29, and 3.30 streams. Claude Code validated that a target file path resided within the project working directory at permission-check time, but re-resolved the path at write time without repeating that validation. An attacker with write access to a shared workspace could exploit this time-of-check to time-of-use (TOCTOU) race condition by atomically replacing a project file with a symbolic link between the permission check and the write operation, causing Claude Code to follow the symlink and write to an arbitrary file outside the project sandbox. Exploitation requires winning a race against the write operation, but could allow a lower-privileged attacker to redirect benign edits to sensitive files (such as shell configuration) in a higher-privileged session, resulting in arbitrary file modification and privilege escalation. Red Hat rates this flaw as moderate impact (CVSS 7.0, AV:L/AC:H/PR:L) because exploitation requires local access with write access to the shared workspace and successfully winning a race; the upstream advisory rates it High (CVSS 7.7) using a CVSS v4 vector that assumes a network attack vector and no privileges. A fix is being pursued for the affected Red Hat OpenShift Dev Spaces streams with the resolution delegated to the responsible component team.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Upstream advises that users on standard Claude Code auto-update have already received the fix and that users performing manual updates should update to the latest version.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spaces 3.31devspaces/pluginregistry-rhel9:1792495212Fixed 2026-10-26RHSA-2026:90321

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

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

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

References

Check your stackJSON