Loading vulnerability…
CVE-2025-53536 affects Roo Code, an AI-powered autonomous coding agent. In versions prior to 3.22.6, if file writes were auto-approved for the agent (specifically when "Write" was auto-approved), an attacker able to submit prompts to the agent could cause it to modify VS Code settings files and thereby achieve code execution. The issue stems from the agent being allowed to perform trusted configuration writes based on attacker-controlled prompt input. One documented exploitation path uses the VS Code setting php.validate.executablePath, which defines the executable invoked for PHP syntax validation. An attacker could write an arbitrary command path into that setting and then create or cause the opening of a PHP file so the IDE triggers the configured executable. This is part of a broader class of prompt-injection-driven IDE/agent abuses in which legitimate IDE features are repurposed for execution.
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.
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.