Local command execution via undisclosed injection
Published Jan 14, 2026 · Updated Jan 14, 2026
Command injection in Spring CLI VSCode Extension 0.9.0 and earlier allows local users to execute commands in the VS Code user's context. Spring has not published the vulnerable function, input source, or command-construction operation. Exploitation requires local low-privileged access and user interaction; successful commands execute on the user's machine.
Summary
What happened
Command injection in Spring CLI VSCode Extension 0.9.0 and earlier allows local users to execute commands in the VS Code user's context. Spring has not published the vulnerable function, input source, or command-construction operation. Exploitation requires local low-privileged access and user interaction; successful commands execute on the user's machine.
The record
- CVE
- CVE-2026-22718
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Spring
- Product
- Spring CLI VSCode Extension
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.9.0 and older
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo