Loading vulnerability…
CVE-2026-39861 affects Claude Code prior to version 2.1.64. The vulnerability is caused by the sandbox allowing sandboxed processes to create symbolic links that point outside the workspace boundary. When Claude Code later wrote to a path that appeared to be inside the workspace but actually resolved through such a symlink, the unsandboxed component followed the symlink and performed the write on the target path outside the workspace without prompting the user. This created a sandbox escape condition through the interaction of two components: the sandboxed process could create the symlink, and the unsandboxed application could subsequently dereference it and write through it. Although neither component alone could directly write outside the workspace, their combination enabled arbitrary file writes outside the intended sandbox scope, with potential follow-on code execution outside the sandbox. The provided context further states that reliable exploitation required introducing untrusted content into a Claude Code context window so that prompt injection could trigger sandboxed code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.