Case · DiggingBeagle record

Claude Code write-time symlink race escaped the project path

Anthropic disclosed a TOCTOU flaw in Claude Code before 2.1.129 where a workspace writer could replace a checked project path with a symlink and redirect the eventual write outside the project.

Scope

Local project-write vulnerability disclosed October 5, 2026, affecting Claude Code versions before 2.1.129.

Assessment profile

Assessment method
Exploitation
not established
Remediation
patch available
AI role
AGAINST AI
Basis and provenance

The vendor advisory confirms CVE-2026-103435, the workspace-write/race prerequisites and patched version 2.1.129. No operational victim evidence or independent retest is present. Primary passages were inspected in this review, but the pinned contract supplies no grading rubric for A-D or the numeric impact bands; both remain ungraded. This is a source review, not an independent reproduction.

Assessed Oct 13, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Checked project edit

    Claude Code approves a target inside the working directory at permission-check time.

    Boundary: The approval is attached to the earlier path resolution.

  2. 02

    Workspace race

    An attacker with workspace write access atomically substitutes a symlink before the actual write.

    Boundary: Path identity changes after approval; exploitation also requires winning the race.

  3. 03

    Redirected write

    The later resolution follows the symlink outside the project, using the writing session's permissions.

    Boundary: A benign edit may affect a file outside the originally approved boundary.

Timeline

  1. Oct 5, 2026
    disclosure

    Public disclosure

Claims & evidence

Implications

Permission decisions about files must remain bound to the same object at write time despite symlink and filesystem changes.

Controls and mitigations

  • Use Claude Code 2.1.129 or later. The vendor reports delivery through standard auto-update, but the active version still determines whether a manually managed installation is covered.

Unknowns and contradictions

  • No confirmed in-the-wild exploitation is reported by the advisory.
  • Exactly which previously authorized project writes were targeted depends on attacker workspace access and race timing.

Sources and citation

Material revision history

  1. Oct 13, 2026 · Published version · first publication · revision 141