Claude Code prompt confirmation bypass leading to file read and network exfiltration
CVE-2025-55284 affects Claude Code prior to version 1.0.4. Due to an overly broad allowlist of commands treated as safe, an attacker can bypass Claude Code confirmation prompts and cause the agent to read local files and transmit their contents over the network without the expected user approval. The issue is exploitable through untrusted content injected into the Claude Code context window, i.e., an indirect prompt-injection scenario in which attacker-controlled content influences agent behavior. Supporting context indicates the vulnerability was used for data exfiltration, including API keys, and could leverage DNS-based techniques to encode and send stolen data.
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
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity Claude Code vulnerability patched in June 2025 that allowed prompt injection to exfiltrate API keys via DNS subdomain encoding.
A vulnerability in Claude Code allowing data exfiltration through DNS-based prompt injection.
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.