Remote code execution via unguarded initializeCommand
Published Jun 13, 2025 · Updated Feb 20, 2026
Command injection in Microsoft Visual Studio 2022 allows remote authenticated users to execute code by inducing a user to open a crafted project. The devcontainer.json handler fails to warn before unsafe initializeCommand actions are processed, allowing project-supplied command text to run in the user's context. Exploitation requires an affected user to open the malicious page or project file, after which injected commands gain that user's privileges.
Summary
What happened
Command injection in Microsoft Visual Studio 2022 allows remote authenticated users to execute code by inducing a user to open a crafted project. The devcontainer.json handler fails to warn before unsafe initializeCommand actions are processed, allowing project-supplied command text to run in the user's context. Exploitation requires an affected user to open the malicious page or project file, after which injected commands gain that user's privileges.
The record
- CVE
- CVE-2025-47959
- Published
- Jun 13, 2025
- Updated
- Feb 20, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2022 version 17.10
- Classifications
- CWE-77, T1203, T1204.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 20, 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=17.10.0 <17.10.16
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