Skip to main content
Mallory
HighVulnerability

CVE-2026-50178: Angular Language Service VS Code Extension JSDoc Hover Command Injection RCE

Published Jun 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS0.50%44th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Angular
IdentifiersCVE-2026-50178CWE-94 · Improper Control of Generation of…

CVE-2026-50178 is a remote code execution vulnerability in the Angular Language Service extension for Visual Studio Code prior to version 21.2.4. The extension configures VS Code’s hover tooltip Markdown renderer with trusted rendering enabled, allowing active elements such as command URIs to be processed. At the same time, the Angular Language Server forwards JSDoc-derived hover content without properly escaping or sanitizing brackets, raw links, and control characters. An attacker can embed a malicious command-bearing link in JSDoc within a project source file or a third-party package dependency. When a developer hovers over the affected symbol and then activates the rendered link, VS Code executes the associated command sequence on the developer workstation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to code execution on the developer’s host through the IDE context. This can enable compromise of the local workstation, theft of source code or credentials accessible to the developer environment, tampering with repositories or build artifacts, and follow-on activity using the developer’s existing permissions and tooling.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, reduce exposure by disabling or restricting use of the vulnerable Angular Language Service extension in VS Code, avoiding untrusted projects and dependencies, and treating hover content from third-party code as untrusted. Limit installation of unreviewed npm dependencies and apply dependency review controls to reduce the chance of malicious JSDoc content entering the workspace.

Remediation

Patch, then assume compromise.

Upgrade the Angular Language Service VS Code extension to version 21.2.4 or later, which fixes the unsafe handling of hover Markdown content. Ensure development environments use the patched extension version across local workstations and managed IDE deployments.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AngularAngular Language Serviceapplication
FAQ

Frequently asked questions

Is CVE-2026-50178 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-50178 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-50178?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-50178.
Is there a patch for CVE-2026-50178?
Upgrade the Angular Language Service VS Code extension to version 21.2.4 or later, which fixes the unsafe handling of hover Markdown content. Ensure development environments use the patched extension version across local workstations and managed IDE deployments.
What products are affected by CVE-2026-50178?
Angular Language Service.
How severe is CVE-2026-50178?
CVE-2026-50178 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.50% (44th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.