CVE-2026-32635 — Angular has XSS in i18n attribute bindings
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+6
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented mitigation — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Angular Angular Cli, Angular Compiler, Angular Core).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Angular | Angular Cli | ≥ 17.0.0 and < 19.2.0≥ 20.0.0 and ≤ 20.3.18≥ 21.0.0 and < 21.2.4version 22.0.0-next0version 22.0.0-next1 | Vulnerable | NIST National Vulnerability Database |
| Angular | Compiler | version >= 22.0.0-next.0, < 22.0.0-next.3version >= 21.0.0-next.0, < 21.2.4version >= 20.0.0-next.0, < 20.3.18version >= 17.0.0.next.0, < 19.2.20 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Angular | Core | version >= 22.0.0-next.0, < 22.0.0-next.3version >= 21.0.0-next.0, < 21.2.4version >= 20.0.0-next.0, < 20.3.18version >= 17.0.0.next.0, < 19.2.20 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.6 | CVSS 4.0 | High | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 8.6 | CVSS 4.0 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
| 9.0 | CVSS 3.1 | Critical | 2.3 | 6.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.50%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · @angular/compiler, @angular/core
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 9.0
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-104871 Angular SSR: Path Traversal to Sibling Directories in CommonEngine on Windows 12d
- Medium CVE-2026-44437 Angular SSR: Open Redirect and Request Steering via Encoded X-Forwarded-Prefix May 13, 2026
- Medium CVE-2026-33397 Angular SSR Vulnerable to Protocol-Relative URL Injection via Single Backslash Bypass Mar 26, 2026
- Critical CVE-2026-27739 Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline Feb 25, 2026
- Medium CVE-2026-27738 Angular SSR has an Open Redirect via X-Forwarded-Prefix Feb 25, 2026
- High CVE-2025-62427 Server-Side Request Forgery (SSRF) in Angular SSR Oct 16, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-32635 is "Angular has XSS in i18n attribute bindings", rated Critical. It affects Angular Cli (Angular); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.0 describes technical severity. EPSS 0.50% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.