CVE-2026-22610
CVE-2026-22610 is a Cross-site Scripting (XSS) vulnerability in @angular/compiler. O3 Security confirms whether CVE-2026-22610 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@angular/compilernpm@angular/corenpmDescription
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @angular/compiler | ≥ 21.1.0-next.0&&< 21.1.0-rc.0 | 21.1.0-rc.0 |
| 📦npm | @angular/core | ≥ 21.1.0-next.0&&< 21.1.0-rc.0 | 21.1.0-rc.0 |
| 📦npm | @angular/compiler | ≥ 21.0.0-next.0&&< 21.0.7 | 21.0.7 |
| 📦npm | @angular/core | ≥ 21.0.0-next.0&&< 21.0.7 | 21.0.7 |
| 📦npm | @angular/compiler | ≥ 20.0.0-next.0&&< 20.3.16 | 20.3.16 |
| 📦npm | @angular/core | ≥ 20.0.0-next.0&&< 20.3.16 | 20.3.16 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/compiler. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @angular/compiler to 21.1.0-rc.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22610 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 pinpoints whether CVE-2026-22610 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-22610. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-22610 in your dependencies?
O3 detects CVE-2026-22610 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.