Code execution via unsanitized executor command
Published Feb 16, 2026 · Updated Feb 16, 2026
Command injection in formulahendry Code Runner 0.12.2 allows attackers to execute arbitrary code when a crafted VS Code workspace is opened. The extension reads a language executor from code-runner.executorMap and passes it unsanitized to child_process.spawn() with shell execution enabled. The user must open the attacker-supplied workspace and invoke Code Runner, after which the command runs with the VS Code user's privileges.
Summary
What happened
Command injection in formulahendry Code Runner 0.12.2 allows attackers to execute arbitrary code when a crafted VS Code workspace is opened. The extension reads a language executor from code-runner.executorMap and passes it unsanitized to child_process.spawn() with shell execution enabled. The user must open the attacker-supplied workspace and invoke Code Runner, after which the command runs with the VS Code user's privileges.
The record
- CVE
- CVE-2025-65715
- Published
- Feb 16, 2026
- Updated
- Feb 16, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1204.002, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 16, 2026CVE publishedPublication date reported by the CVE source.
- Feb 16, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- OX Security reverse-shell proof of conceptproof of concept · demonstrated
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