Loading vulnerability…
CVE-2026-22718 is a command injection vulnerability in the Spring CLI extension for Visual Studio Code (Spring CLI VSCode Extension) affecting version 0.9.0 and earlier. Due to unsafe handling of input used to construct/execute system commands, an attacker can manipulate extension-controlled inputs to inject additional shell commands, resulting in arbitrary command execution on the developer’s machine under the privileges of the logged-in user. Reported exploitation scenarios include normal extension usage such as opening a malicious project or interacting with a crafted file that influences the extension’s command invocation.
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 local command injection vulnerability in the Spring CLI VSCode Extension that can allow arbitrary command execution on a developer machine when triggered with user interaction.
A command injection vulnerability in the Spring CLI extension for Visual Studio Code that can allow arbitrary command execution on a developer’s machine (e.g., via opening a malicious project or crafted file).
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.