CVE-2026-22610: Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
Noroxi assessment
Priority: Monitor (action score 34/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- Fixed version: @angular/compiler (npm) 19.2.18, 20.3.16, 21.0.7; @angular/core (npm) 19.2.18, 20.3.16, 21.0.7.
Low priority for now. Upgrade to @angular/compiler (npm) 19.2.18, 20.3.16, 21.0.7; @angular/core (npm) 19.2.18, 20.3.16, 21.0.7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 10, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-79
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is the Angular on your site affected?Scan JavaScript libraries
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| angular | angular | cpe:2.3:a:angular:angular |
Is the Angular on your site affected?
The free JavaScript library scanner reads the Angular version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.
Scan JavaScript librariesVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
angular angular
- >= 21.1.0-next.0, < 21.1.0-rc.0, >= 21.0.0-next.0, < 21.0.7, >= 20.0.0-next.0, < 20.3.16, < 19.2.18affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- angular angularup to 18.2.14 inclusive
- angular angular19.0.0 and later · before 19.2.18
- angular angular20.0.0 and later · before 20.3.16
- angular angular21.0.0 and later · before 21.0.7
- angular angular21.1.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @angular/compiler | from 19.0.0-next.0 · before 19.2.18 | 19.2.18 |
| npm | @angular/compiler | from 20.0.0-next.0 · before 20.3.16 | 20.3.16 |
| npm | @angular/compiler | from 21.0.0-next.0 · before 21.0.7 | 21.0.7 |
| npm | @angular/compiler | from 21.1.0-next.0 · before 21.1.0-rc.0 | 21.1.0-rc.0 |
| npm | @angular/compiler | up to and including 18.2.14 | — |
| npm | @angular/core | from 19.0.0-next.0 · before 19.2.18 | 19.2.18 |
| npm | @angular/core | from 20.0.0-next.0 · before 20.3.16 | 20.3.16 |
| npm | @angular/core | from 21.0.0-next.0 · before 21.0.7 | 21.0.7 |
| npm | @angular/core | from 21.1.0-next.0 · before 21.1.0-rc.0 | 21.1.0-rc.0 |
| npm | @angular/core | up to and including 18.2.14 | — |
Same product
angular: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-68945Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning35Monitor
- CVE-2026-50168Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass35Monitor
- CVE-2026-46417Angular: SSRF via Hostname Hijacking in @angular/platform-server35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-66035Nov 26, 2025 · Angular HTTP Client Has XSRF Token Leakage via Protocol-Relative URLs30Monitor
- ← EarlierCVE-2025-66412Dec 1, 2025 · Angular Stored XSS Vulnerability via SVG Animation, SVG URL and MathML Attributes34Monitor
- Later →CVE-2026-27970Feb 25, 2026 · Angular i18n vulnerable to Cross-Site Scripting (XSS)30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:@angular/compiler | 19.2.18 | Package registry (OSV) |
| npm:@angular/compiler | 20.3.16 | Package registry (OSV) |
| npm:@angular/compiler | 21.0.7 | Package registry (OSV) |
| npm:@angular/compiler | 21.1.0-rc.0 | Package registry (OSV) |
| npm:@angular/core | 19.2.18 | Package registry (OSV) |
| npm:@angular/core | 20.3.16 | Package registry (OSV) |
| npm:@angular/core | 21.0.7 | Package registry (OSV) |
| npm:@angular/core | 21.1.0-rc.0 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2026-01-18 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+8 d
- TodayNov 12, 2026+307 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-6641240 days apartAngular Stored XSS Vulnerability via SVG Animation, SVG URL and MathML Attributes34Monitor
- CVE-2026-50555163 days apartAngular: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in @angular/platform-server34Monitor
- CVE-2026-50556163 days apartAngular: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR34Monitor
- CVE-2026-54267163 days apartAngular Client Hydration DOM Clobbering & Response-Cache Poisoning34Monitor
- CVE-2026-69149205 days apartAngular SSR: Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS)34Monitor
- CVE-2026-88058243 days apartAngular: SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements34Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.