CVE-2026-49241: Angular Language Service VS Code Extension Arbitrary Code Execution

Technical summary

The vulnerability stems from unsafe dynamic module resolution in the Angular Language Service extension's client component. The extension reads TypeScript SDK path settings (typescript.tsdk and js/ts.tsdk.path) from workspace configuration files (.vscode/settings.json) without validating VS Code's Workspace Trust state or user consent. These untrusted paths are passed as command-line arguments to the background Node.js language server. During initialization, the language server calls require() to load tsserverlibrary.js from the attacker-controlled path, resulting in arbitrary code execution with the privileges of the Node.js process. This bypasses normal security prompts and trust mechanisms. The fix in 21.2.4 addresses the unsafe path handling and dynamic import logic.

Business impact

Developers using affected versions of the extension face supply-chain compromise risk when cloning or working with untrusted repositories. An attacker can execute arbitrary code on a developer's machine with the same privileges as the VS Code language server process, potentially leading to theft of credentials, source code exfiltration, installation of persistent backdoors, or lateral movement within corporate networks. For organizations with developers contributing to open-source projects or evaluating external code, this risk is particularly acute. The silent, background nature of the attack—no visible prompts or warnings—increases the likelihood of successful compromise.

Affected systems

The Angular Language Service VS Code Extension versions prior to 21.2.4 are affected. The vulnerability applies to any developer or organization using the extension to edit Angular templates in VS Code, regardless of operating system. The attack requires a developer to open a malicious repository in VS Code; it does not execute during clone or file browsing alone, but rather when the extension initializes its language server process.

Exploitability

Exploitability is high and requires only user interaction (opening a folder in VS Code), not elevated privileges or special network access. An attacker must craft a malicious repository with a fake tsserverlibrary.js file and matching .vscode/settings.json configuration, then distribute it through public repositories, email, or social engineering. Once a developer opens the folder, the malicious code executes automatically in the background without visible warnings. No specialized tools or knowledge of the extension internals is required to weaponize this attack; it is practical and scalable.

Remediation

Users must upgrade the Angular Language Service VS Code Extension to version 21.2.4 or later. Additionally, developers should review any .vscode/settings.json files in open repositories for suspicious typescript.tsdk or js/ts.tsdk.path entries pointing to non-standard locations. Organizations should enforce extension version pinning and provide security awareness training on the risks of opening untrusted repositories. Enabling VS Code's Workspace Trust feature (introduced in VS Code 1.52) provides a secondary control, though it does not prevent this specific attack without proper extension hardening.

Patch guidance

Update the Angular Language Service extension to 21.2.4 or later via the VS Code Extensions marketplace or command line (code --install-extension Angular.ng-template). Verify the update is applied by checking the extension version in VS Code's Extensions panel (Ctrl+Shift+X / Cmd+Shift+X). No configuration changes are required post-update; the patched version handles workspace settings securely. Organizations managing extensions centrally should stage and test the update in non-critical development environments before broad rollout.

Detection guidance

Monitor for unexpected or unauthorized Node.js child processes spawned by VS Code, particularly those with --tsdk command-line arguments pointing to unusual paths. Review .vscode/settings.json files in repositories for typescript.tsdk or js/ts.tsdk.path entries that reference subdirectories outside standard Node.js installation paths. Scan repositories for tsserverlibrary.js files not in the expected node_modules directory. In enterprise environments, use endpoint detection and response (EDR) tools to flag file modifications or execution from suspicious VS Code workspace directories. Additionally, monitor for exfiltration or credential access following VS Code language server initialization.

Why prioritize this

This vulnerability merits immediate attention due to its high CVSS score (8.8), practical exploitability, and silent execution model. The attack bypasses user awareness by running in the background without visible prompts, making it effective against security-conscious developers. The supply-chain nature—targeting development environments rather than production systems—creates a bridgehead for broader organizational compromise. While not yet listed on CISA's Known Exploited Vulnerabilities catalog, the low barrier to exploitation and widespread use of VS Code in development teams makes it an attractive target for sophisticated threat actors.

Risk score, explained

CVSS 8.8 (High) reflects the combination of network attack vector (malicious repository distribution), low complexity, no privilege requirements, user interaction (opening a folder), and high impact on confidentiality, integrity, and availability. The score accurately captures the severity: arbitrary code execution on a developer's machine with no authentication or privilege escalation needed. However, impact is somewhat localized to the individual developer's environment unless that developer has privileged access to shared systems or source code repositories. Organizations should treat this as a high-priority, high-visibility vulnerability given its targeting of development infrastructure.

Frequently asked questions