Rejected CVE-2026-35021: OS command injection in Anthropic Claude Code CLI prompt editor invocation utility
CVE-2026-35021 was rejected by its CNA. The rejection states that the affected code path cannot be triggered through normal usage of Claude Code. Although third-party reporting described an OS command injection issue in the prompt editor invocation utility of Anthropic Claude Code CLI and the Claude Agent SDK—where attacker-controlled file paths containing shell metacharacters such as $() or backticks were allegedly interpolated into shell commands executed via execSync—this CVE record is not considered a valid, exploitable vulnerability by the assigning authority based on the available information in the CVE entry.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.