Loading vulnerability…
CVE-2025-58372 is a high-severity vulnerability in Roo Code, an AI-powered autonomous coding agent for editors, affecting versions 3.25.23 and earlier. The flaw exists because certain VS Code workspace configuration files with the .code-workspace extension were not protected equivalently to the .vscode directory. In configurations where Roo Code is allowed to auto-approve file writes, an attacker who can influence the agent's prompts, including via prompt injection, can cause malicious workspace settings or task definitions to be written into a workspace configuration file. When the victim later reopens the workspace, those malicious tasks or settings may be executed automatically, leading to arbitrary code execution on the local system.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Roo Code AI IDE where prompt injection can be used to edit workspace configuration files and override settings to achieve code execution.
A potential remote code execution vulnerability in Roo Code caused by insufficient protection of .code-workspace files, allowing malicious workspace settings or tasks to be written and later executed when the workspace is reopened.
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.