Quick answers
- Is CVE-2026-86063 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86063 being exploited in the wild.
- How severe is CVE-2026-86063?
- High severity, with a CVSS score of 4, published 15 October 2026.
- Which products and versions are affected?
- Anthropic Claude Code < 2.1.179; Anthropic Claude Desktop < 2.1.179; @anthropic-ai/claude-code (npm) < 2.1.179, SEMVER:introduced=0,fixed=2.1.179.
- Is there a fix for CVE-2026-86063?
- Yes. @anthropic-ai/claude-code (npm): upgrade to 2.1.179 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86063 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86063?
- Check whether you run Anthropic Claude Code, Anthropic Claude Desktop or @anthropic-ai/claude-code (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @anthropic-ai/claude-code (npm): upgrade to 2.1.179 or later
npm install @anthropic-ai/claude-code@2.1.179
Technical details
The plugin installer uses `git checkout` to fetch a pinned commit SHA but fails to verify that the resulting HEAD matches the intended hash. An attacker can create a branch whose name is a valid 40-character SHA, causing git to resolve the checkout to the attacker's branch tip rather than the pinned commit. This requires the user to install a malicious plugin and for the hosting platform to allow SHA-shaped branch names; the verification bypass enables code execution with user privileges.
Affected products
- Anthropic Claude Code < 2.1.179
- Anthropic Claude Desktop < 2.1.179
Identifiers
- CVE-2026-86063
- GHSA-pq7j-f95f-qfcv
Timeline
- 2026-10-09: disclosed
- 2026-10-15: advisory