Skip to main content
VulnerabilityPublished

CVE-2025-59536: anthropics claude-code · Code Injection

Affects anthropics claude-codeSource CVE Database V5

0

Not known to be exploited · 27% EPSS · CVSS 8.7 High : upgrade to 1.0.111 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
27.2% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.111
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade anthropics claude-code to 1.0.111.

Affected software

ProductAffectedFixed in
anthropics claude-codeAffected
  • <1.0.111
Fixed in
  • 1.0.111

AI-suggested

  1. Immediately update all instances of anthropics Claude Code to version 1.0.111 or later to ensure the vulnerability is patched.
  2. Disable or restrict the ability to open projects from untrusted directories, enforcing strict workspace trust policies within development teams.
  3. Educate developers and users about the risks of opening untrusted project directories and the importance of verifying project sources before loading.
  4. Implement endpoint security controls that monitor and restrict unauthorized code execution within developer environments.
  5. Integrate runtime application self-protection (RASP) or behavior monitoring to detect anomalous code execution patterns originating from Claude Code processes.
  6. Review and harden CI/CD pipelines to prevent injection of malicious code from compromised developer workstations.
  7. For organizations performing manual updates, establish automated patch management processes to reduce update delays.
  8. Conduct regular security audits of developer tools and their configurations to identify and remediate trust-related vulnerabilities.
  9. Consider network segmentation to isolate development environments from critical production systems to limit lateral movement in case of compromise.

Description

Claude Code is an agentic coding tool. Versions before 1.0.111 were vulnerable to Code Injection due to a bug in the startup trust dialog implementation. Claude Code could be tricked to execute code contained in a project before the user accepted the startup trust dialog. Exploiting this requires a user to start Claude Code in an untrusted directory. Users on standard Claude Code auto-update will have received this fix automatically. Users performing manual updates are advised to update to the latest version. This issue is fixed in version 1.0.111.

References

Community reviews

Loading reviews…