Loading vulnerability…
CVE-2026-25724 is a symbolic link handling flaw in Anthropic Claude Code prior to version 2.1.7. The product did not strictly enforce file access deny rules configured in settings.json when a requested path was a symbolic link. If access to a sensitive file was explicitly denied, Claude Code could still read that file by accessing a permitted symlink that resolved to the denied target. The vulnerability stems from validating the apparent link path rather than consistently enforcing policy on the canonical resolved destination, creating a path resolution mismatch between the security check and the filesystem object actually opened.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously fixed Claude Code symbolic-link/path validation flaw in the permission subsystem, cited as prior related background to the newly disclosed issue.
A previously fixed Claude Code symbolic-link path validation flaw in the permission subsystem, where security checks evaluated one path while the filesystem resolved a different symlink target.
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.