Skip to main content
Mallory
HighVulnerability

CVE-2025-66412: Stored XSS in Angular Template Compiler

Published Dec 1, 2025 · Updated 24 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.5High · v4
EPSS0.38%33rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Angular
IdentifiersCVE-2025-66412CWE-79 · Improper Neutralization of Input…

CVE-2025-66412 is a stored cross-site scripting vulnerability in the Angular Template Compiler caused by an incomplete internal security schema. Certain SVG and MathML URL-bearing attributes are not classified as requiring URL sanitization, and SVG animation attributeName validation is insufficient. Attacker-controlled bindings can consequently bypass Angular's built-in sanitization and introduce executable JavaScript URLs. The vulnerability affects releases before the corresponding fixed versions in the Angular 19, 20, and 21 release lines: 19.2.17, 20.3.15, and 21.0.2.

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 executes attacker-controlled JavaScript in the vulnerable application's origin. This can enable theft of script-accessible authentication tokens and sensitive data, session compromise, data exfiltration, and unauthorized actions using the victim's application privileges. The impact is browser-side script execution; server-side code execution is not established.

Mitigation

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

Until upgrading, prevent untrusted data from reaching affected SVG/MathML URL-bearing attribute bindings, including [attr.xlink:href]. Avoid attacker-controlled attributeName bindings on SVG animate, set, animateMotion, and animateTransform elements. Deploy a restrictive Content Security Policy that blocks JavaScript URL execution as defense in depth. For affected SIDIS Prime deployments, restrict network access using appropriate access controls; this does not replace correcting vulnerable bindings or applying the update.

Remediation

Patch, then assume compromise.

Upgrade @angular/compiler to 19.2.17, 20.3.15, or 21.0.2, or a later fixed release in the applicable release line. For Siemens SIDIS Prime deployments containing the affected component, upgrade SIDIS Prime to V4.0.800 or later using the vendor-supported product update rather than independently replacing bundled dependencies.

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
AngularAngularapplication
FAQ

Frequently asked questions

Is CVE-2025-66412 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2025-66412 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-66412?
As of Oct 25, 2026, Mallory has found no public exploit for CVE-2025-66412.
Is there a patch for CVE-2025-66412?
Upgrade @angular/compiler to 19.2.17, 20.3.15, or 21.0.2, or a later fixed release in the applicable release line. For Siemens SIDIS Prime deployments containing the affected component, upgrade SIDIS Prime to V4.0.800 or later using the vendor-supported product update rather than independently replacing bundled dependencies.
What products are affected by CVE-2025-66412?
Angular.
How severe is CVE-2025-66412?
CVE-2025-66412 has a CVSS v4 score of 8.5 (High) and an EPSS score of 0.38% (33rd percentile) as of Oct 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 activity5Community discussion across Reddit, Mastodon, and other social sources.