CVE-2026-49241 is a high-severity remote code execution vulnerability in the Angular Language Service VS Code Extension prior to version 21.2.4. The extension reads custom TypeScript SDK path settings from workspace configuration, including typescript.tsdk and js/ts.tsdk.path, without validating VS Code Workspace Trust state or obtaining explicit user consent. The client component forwards the workspace-supplied path to the background Node.js language server using the --tsdk argument. During initialization, the language server resolves and loads tsserverlibrary.js relative to that attacker-controlled directory using Node.js module loading. A malicious repository can therefore supply a crafted workspace configuration together with a rogue tsserverlibrary.js in a referenced local folder, causing arbitrary JavaScript execution when the repository is opened in VS Code and the extension initializes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.