Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious repo with poisoned settings.json
-
DeliveryDeveloper opens workspace in VS Code
-
ExploitDeveloper triggers generator install/uninstall
-
ExecutionUnsanitized value reaches execSync shell string
-
ImpactArbitrary OS commands run as developer
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the SAP Yeoman UI (app-studio-toolkit) extension be installed in VS Code, and that the victim developer open an attacker-controlled workspace repository containing a crafted settings.json which sets the ApplicationWizard.installationLocation configuration value to an injected shell command. The command only fires when the developer triggers a generator installation or uninstallation, which invokes child_process.execSync with the unsanitized value as a shell string. Limiting factors: the attack depends on social engineering (the developer must clone/open the malicious project and then initiate a generator action), it runs only with the developer's own privileges, and it is confined to developer workstations rather than servers - there is no unauthenticated remote-service exposure. |
| Impact | The input CVSS 3.1 base score is 5.9 (Medium) with vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N. Several signals conflict and should be verified. First, the vector marks UI:N (no user interaction), but the description explicitly requires a developer to open a malicious workspace and trigger a generator installation - that is effectively active user interaction, so UI:N appears understated. Second, AV:N (network) is questionable: the injection vector is a settings.json inside a workspace repository opened locally in VS Code, which is closer to a local/workspace attack than a direct network-service exploit. Third, the impact metrics C:H/I:L/A:N undersell the outcome - arbitrary OS command execution with the developer's privileges realistically yields full confidentiality, integrity, and availability impact. No EPSS score, CISA KEV listing, or public POC was provided, so exploitation likelihood cannot be quantified from the data; status is 'no public exploit identified at time of analysis.' Net real-world risk is moderate and gated by social engineering (the developer must clone/open an attacker-controlled repo and run a generator), but the consequence (code execution as the developer, a common path to credential and source-code theft in dev environments) is severe. This is a credible developer-supply-chain risk for SAP tooling users rather than a mass-exploitable internet-facing flaw. |
| Exploit ScenarioDerived | An attacker publishes a malicious repository (e.g., a tempting SAP sample project) containing a crafted .vscode/settings.json that sets ApplicationWizard.installationLocation to a value embedding shell metacharacters and commands. A developer clones and opens the project in VS Code with the SAP Yeoman UI extension and triggers a generator install/uninstall, causing child_process.execSync to run the injected commands with the developer's privileges. No public exploit code was identified in the provided data, but the technique is straightforward shell injection. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Command injection in SAP Yeoman UI (app-studio-toolkit) enables an attacker to execute arbitrary OS commands with the developer's privileges by crafting a malicious workspace settings.json that sets ApplicationWizard.installationLocation to a shell payload. The command fires when the developer triggers a generator installation or uninstallation, which invokes child_process.execSync with the unsanitized value. The assessed CVSS vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates local exploitation requiring user interaction, with high impact to confidentiality, integrity, and availability on the developer workstation; no confirmed active exploitation or public exploit code is identified in the provided data.
RemediationAI
No specific patched version is identified in the provided data; consult the SAP Security Patch Day page at https://url.sap/sapsecuritypatchday and the GitHub advisory GHSA-vm9q-mf35-jwpx for the latest fix. Until a patch is applied, mitigate by not opening untrusted workspace repositories in VS Code when the SAP Yeoman UI extension is installed. Enable VS Code's Workspace Trust feature to prevent automatic execution of workspace settings from untrusted folders, though this may block legitimate functionality. Alternatively, disable the SAP Yeoman UI extension when working with untrusted code, but this prevents generator installation and uninstallation. Developers should review .vscode/settings.json for suspicious values in ApplicationWizard.installationLocation before triggering generator actions. Avoid setting ApplicationWizard.installationLocation to values containing shell metacharacters such as ;, |, &, $, or backticks.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic OS command injection (CWE-78) in the SAP Yeoman UI VS Code extension (app-studio-toolkit). The extension uses Node.js child_process.execSync to run shell commands for installing and uninstalling Yeoman generators. It constructs a shell string that includes the value of the VS Code workspace configuration ApplicationWizard.installationLocation without sanitization. A developer who opens a malicious repository with a crafted .vscode/settings.json containing shell metacharacters (e.g., semicolons, backticks, $()) in that setting will execute injected commands when they initiate a generator installation or uninstallation. The CPE cpe:2.3:a:sap_se:sap_yeoman-ui:*:*:*:*:*:*:*:* indicates all versions of the product are potentially affected. The root cause is the failure to separate data from code when invoking a shell, allowing untrusted configuration to be interpreted as commands.
Know when Visual Studio Code gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
Injection via a locally opened workspace settings file means AV:L and UI:R (developer must open repo and trigger a generator); attacker needs no victim privileges (PR:N) and arbitrary command execution yields full C/I/A.
Primary rating from Vendor (sap).
CVSS VectorVendor: sap
DescriptionCVE.org
The affected code used child_process.execSync with a shell string for generator installation and uninstallation. This allowed an attacker to execute arbitrary OS commands with the developer's privileges by manipulating the ApplicationWizard.installationLocation VS Code workspace configuration value. Because the value was passed directly to the shell without sanitisation, a malicious workspace repository could craft a settings.json that injects OS commands when a developer opens the project and triggers a generator installation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
More in Visual Studio Code
View allVisual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authent
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely e
Security-feature bypass in Microsoft Visual Studio Code before 1.136.2 lets a remote, unauthenticated attacker defeat a
Remote code execution in Visual Studio Code (versions 1.0.0 up to but not including 1.141.1) is achievable through a pat
Privilege escalation in Microsoft Visual Studio Code allows remote unauthenticated attackers to elevate privileges over
Visual Studio Code Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authent
Security-feature bypass in Microsoft Visual Studio Code lets a remote attacker deliver functionality from an untrusted c
Remote code execution in Visual Studio Code (versions 1.0.0 through 1.132.0) is enabled by a missing authorization check
Command injection in Visual Studio Code 1.0.0 through 1.141.0 allows an unauthenticated remote attacker to execute arbit
Remote code execution in Microsoft Visual Studio Code allows a network-based attacker to inject and execute arbitrary co
Remote code execution in Visual Studio Code versions 1.0.0 through 1.141.1 allows an unauthenticated, network-positioned
Authorization bypass in Visual Studio Code versions 1.0.0 through 1.136.1 allows an unauthenticated network attacker to
EUVD-2026-98196
GHSA-w326-3fj2-854r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB