Loading vulnerability…
CVE-2025-59829 is a symbolic link handling flaw in Claude Code affecting versions prior to 1.0.120. The product’s permission deny logic failed to correctly account for symlink resolution when evaluating whether access to a file should be blocked. As a result, if access to a target file was explicitly denied but Claude Code was permitted to access a symlink that resolved to that same file, the tool could still read the denied file through the symlink path. The vulnerability is a path validation and authorization bypass issue caused by checking the apparent path rather than the canonical resolved target.
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.
3 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 research/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.