Skip to main content
VulnerabilityPublished

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

Affects @anthropic-ai/claude-codeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 2.1.129 soon.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.129
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade @anthropic-ai/claude-code to 2.1.129.

Affected software

ProductAffectedFixed in
Anthropic@anthropic-ai/claude-codeAffected
  • <2.1.129
Fixed in
  • 2.1.129

AI-suggested

Users on the standard Claude Code auto-update channel have already received the fix. Users who perform manual updates should upgrade to the latest version of @anthropic-ai/claude-code to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

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.

References

Community reviews

Loading reviews…