CVE-2026-32635
CVE-2026-32635 is a Cross-site Scripting (XSS) vulnerability in @angular/core. O3 Security confirms whether CVE-2026-32635 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Angular has XSS in i18n attribute bindings
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@angular/corenpmDescription
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-next.3, 21.2.4, 20.3.18, and 19.2.20, a Cross-Site Scripting (XSS) vulnerability has been identified in the Angular runtime and compiler. It occurs when the application uses a security-sensitive attribute (for example href on an anchor tag) together with Angular's ability to internationalize attributes. Enabling internationalization for the sensitive attribute by adding i18n-<attribute> name bypasses Angular's built-in sanitization mechanism, which when combined with a data binding to untrusted user-generated data can allow an attacker to inject a malicious script. This vulnerability is fixed in 22.0.0-next.3, 21.2.4, 20.3.18, and 19.2.20.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @angular/core | ≥ 22.0.0-next.0&&< 22.0.0-next.3 | 22.0.0-next.3 |
| 📦npm | @angular/core | ≥ 21.0.0-next.0&&< 21.2.4 | 21.2.4 |
| 📦npm | @angular/core | ≥ 20.0.0-next.0.0.0&&< 20.3.18 | 20.3.18 |
| 📦npm | @angular/core | ≥ 19.0.0-next.0&&< 19.2.20 | 19.2.20 |
| 📦npm | @angular/core | ≥ 17.0.0-next.0 | No fix |
| 📦npm | @angular/compiler | ≥ 22.0.0-next.0&&< 22.0.0-next.3 | 22.0.0-next.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/core. 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/core to 22.0.0-next.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32635 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-32635 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-32635. 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-32635 in your dependencies?
O3 detects CVE-2026-32635 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.