Loading vulnerability…
CVE-2025-53097 affects Roo Code, an AI-powered autonomous coding agent, prior to version 3.20.3. The vulnerability is caused by the agent's search_files tool failing to honor the setting intended to prevent reads outside the VS Code workspace. As a result, if an attacker can influence the agent through prompt injection or a similar control vector, the agent may read sensitive files from outside the workspace boundary. The disclosed attack path then uses the agent to write the stolen data into a JSON schema location. Because schema fetching in VS Code is enabled by default, this write can trigger an outbound network request automatically, creating a practical exfiltration channel without giving the user an opportunity to deny the request. The issue is therefore a workspace-boundary bypass that enables unauthorized file disclosure and exfiltration through legitimate IDE functionality.
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.
search_files tool respects the configuration limiting file access to the VS Code workspace, thereby preventing reads outside the workspace boundary and reducing the damage possible from prompt injection or other agent-compromise vectors.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.
4 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.