CVE-2025-66412 — @angular/compiler
Fix: angular/angular@1c6b070CVE-2025-66412 is a Cross-site Scripting (XSS) vulnerability in @angular/compiler. A fix is available for @angular/compiler — see the affected versions and patch details below.
Angular Stored XSS Vulnerability via SVG Animation, SVG URL and MathML Attributes
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66412.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@angular/compilernpmDescription
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 21.0.2, 20.3.15, and 19.2.17, A Stored Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. It occurs because the compiler's internal security schema is incomplete, allowing attackers to bypass Angular's built-in security sanitization. Specifically, the schema fails to classify certain URL-holding attributes (e.g., those that could contain javascript: URLs) as requiring strict URL security, enabling the injection of malicious scripts. This vulnerability is fixed in 21.0.2, 20.3.15, and 19.2.17.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @angular/compiler | ≥ 21.0.0-next.0&&< 21.0.2 | 21.0.2npm install @angular/compiler@21.0.2 |
| 📦npm | @angular/compiler | ≥ 20.0.0-next.0&&< 20.3.15 | 20.3.15npm install @angular/compiler@20.3.15 |
| 📦npm | @angular/compiler | ≥ 19.0.0-next.0&&< 19.2.17 | 19.2.17npm install @angular/compiler@19.2.17 |
| 📦npm | @angular/compiler | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/compiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @angular/compiler to 21.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66412 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-66412 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-66412. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | eap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap | RHSA-2026:33371 |
Frequently Asked Questions
Is CVE-2025-66412 in your dependencies?
O3 Security finds CVE-2025-66412 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.