# CVE-2026-22610: Angular has XSS Vulnerability via Unsanitized SVG Script Attributes

> Attackers can execute arbitrary scripts via unsanitized SVG script attributes in Angular applications, requiring an upgrade to patched versions.

- **Severity:** High 8.5 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jan 2026
- **Updated:** 2 Jun 2026
- **Also known as:** CLSA-2026-1774657389, CLSA-2026-1775176141, CLSA-2026-1775176145, CLSA-2026-1775176149, CLSA-2026-1775176156, CLSA-2026-1775176158, CLSA-2026-1775176160, CLSA-2026-1775176162, CLSA-2026-1775176164, CLSA-2026-1775176168, CLSA-2026-1775176171, CLSA-2026-1775176177, CLSA-2026-1775176185, CLSA-2026-1792160980, CLSA-2026-1792161082, CLSA-2026-1792161086, CLSA-2026-1792161088, CLSA-2026-1792161089, CLSA-2026-1792161094, CLSA-2026-1792161096, CLSA-2026-1792161098, CLSA-2026-1792161099, CLSA-2026-1792161101, CLSA-2026-1792161103, CLSA-2026-1792161105, CLSA-2026-1792161108, CLSA-2026-1792161113, CLSA-2026-1792163469, CLSA-2026-1792163471, CLSA-2026-1792163473, CLSA-2026-1792163475, CLSA-2026-1792163481, CLSA-2026-1792163483, CLSA-2026-1792163485, CLSA-2026-1792163487, CLSA-2026-1792163489, CLSA-2026-1792163492, CLSA-2026-1792163496, CLSA-2026-1792163501, CLSA-2026-1792208078, CLSA-2026-1792208082, CLSA-2026-1792208083, CLSA-2026-1792208085, CLSA-2026-1792208450, CLSA-2026-1792208454, CLSA-2026-1792208496, CLSA-2026-1792208500, CLSA-2026-1792208501, CLSA-2026-1792208503, CLSA-2026-1792208516, CLSA-2026-1792208527, CLSA-2026-1792208539, CLSA-2026-1792250186, CLSA-2026-1792250189, CLSA-2026-1792250191, CLSA-2026-1792250193, CLSA-2026-1792250195, CLSA-2026-1792250470, CLSA-2026-1792250517, CLSA-2026-1792250518, CLSA-2026-1792250520, CLSA-2026-1792250521, CLSA-2026-1792250561, CLSA-2026-1792250563, CLSA-2026-1792250592, CLSA-2026-1792281027, CLSA-2026-1792281031, CLSA-2026-1792281032, CLSA-2026-1792281698, CLSA-2026-1792281702, CLSA-2026-1792281704, CLSA-2026-1792281705, CLSA-2026-1792281706, CLSA-2026-1792281707, CLSA-2026-1792281708, CLSA-2026-1792281800, CLSA-2026-1792281802, CLSA-2026-1792281803, CLSA-2026-1792325293, CLSA-2026-1792325296, CLSA-2026-1792325298, CLSA-2026-1792325302, CLSA-2026-1792325303, CLSA-2026-1792325925, CLSA-2026-1792325929, CLSA-2026-1792325930, CLSA-2026-1792326019, CLSA-2026-1792326021, CLSA-2026-1792326022, CLSA-2026-1792326040, CLSA-2026-1792326041, CLSA-2026-1792345153, CLSA-2026-1792345156, CLSA-2026-1792345159, CLSA-2026-1792345161, CLSA-2026-1792345628, CLSA-2026-1792345632, CLSA-2026-1792345634, CLSA-2026-1792345635, CLSA-2026-1792345682, CLSA-2026-1792345685, CLSA-2026-1792345687, CLSA-2026-1792345699, CLSA-2026-1792345721, CLSA-2026-1792357202, CLSA-2026-1792357205, CLSA-2026-1792357207, CLSA-2026-1792357210, CLSA-2026-1792357215, CLSA-2026-1792357766, CLSA-2026-1792357768, CLSA-2026-1792357769, CLSA-2026-1792358023, CLSA-2026-1792358026, CLSA-2026-1792358027, CLSA-2026-1792358061, CLSA-2026-1792366519, CLSA-2026-1792366522, CLSA-2026-1792366524, CLSA-2026-1792366525, CLSA-2026-1792366527, CLSA-2026-1792366529, CLSA-2026-1792366874, CLSA-2026-1792366879, CLSA-2026-1792366893, CLSA-2026-1792366895, CLSA-2026-1792366936, CLSA-2026-1792366937, CLSA-2026-1792366938, CLSA-2026-1792371582, CLSA-2026-1792371586, CLSA-2026-1792371997, CLSA-2026-1792371998, CLSA-2026-1792372000, CLSA-2026-1792372001, CLSA-2026-1792372047, CLSA-2026-1792372048, CLSA-2026-1792372064, CLSA-2026-1792375675, CLSA-2026-1792375678, CLSA-2026-1792375680, CLSA-2026-1792375682, CLSA-2026-1792375683, CLSA-2026-1792375684, CLSA-2026-1792376049, CLSA-2026-1792376053, CLSA-2026-1792376070, CLSA-2026-1792376071, CLSA-2026-1792376074, CLSA-2026-1792376108, CLSA-2026-1792376113, CLSA-2026-1792379935, CLSA-2026-1792379938, CLSA-2026-1792380378, CLSA-2026-1792380379, CLSA-2026-1792380383, CLSA-2026-1792380384, CLSA-2026-1792380404, CLSA-2026-1792380406, CLSA-2026-1792380418, CLSA-2026-1792380429, CLSA-2026-1792380440, CLSA-2026-1792380445, CLSA-2026-1792380446, CLSA-2026-1792382566, CLSA-2026-1792382569, CLSA-2026-1792382571, CLSA-2026-1792382573, CLSA-2026-1792382574, CLSA-2026-1792382576, CLSA-2026-1792382904, CLSA-2026-1792382922, CLSA-2026-1792382923, CLSA-2026-1792382935, CLSA-2026-1792382956, CLSA-2026-1792382960, CLSA-2026-1792382989, CLSA-2026-1792386040, CLSA-2026-1792386043, CLSA-2026-1792386045, CLSA-2026-1792386047, CLSA-2026-1792386410, CLSA-2026-1792386414, CLSA-2026-1792386415, CLSA-2026-1792386434, CLSA-2026-1792386436, CLSA-2026-1792386438, CLSA-2026-1792386439, CLSA-2026-1792386480, CLSA-2026-1792386483, GHSA-jrmj-c5cx-3cw6, UBUNTU-CVE-2026-22610

## What is CVE-2026-22610?

CVE-2026-22610 is a high-severity cross-site scripting vulnerability in angular, published on 10 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-22610?

20 open source packages ship an affected version, including @angular/compiler and @angular/core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@angular/compiler` | npm | All versions to 18.2.14 | None |
| `@angular/compiler` | npm | All versions to 18.2.14 | None |
| `@angular/compiler` | npm | From 19.0.0-next.0 | 19.2.18 |
| `@angular/compiler` | npm | From 19.0.0-next.0 | 19.2.18 |
| `@angular/compiler` | npm | From 20.0.0-next.0 | 20.3.16 |
| `@angular/compiler` | npm | From 20.0.0-next.0 | 20.3.16 |
| `@angular/compiler` | npm | From 21.0.0-next.0 | 21.0.7 |
| `@angular/compiler` | npm | From 21.0.0-next.0 | 21.0.7 |
| `@angular/compiler` | npm | From 21.1.0-next.0 | 21.1.0-rc.0 |
| `@angular/compiler` | npm | From 21.1.0-next.0 | 21.1.0-rc.0 |
| `@angular/core` | npm | All versions to 18.2.14 | None |
| `@angular/core` | npm | All versions to 18.2.14 | None |
| `@angular/core` | npm | From 19.0.0-next.0 | 19.2.18 |
| `@angular/core` | npm | From 19.0.0-next.0 | 19.2.18 |
| `@angular/core` | npm | From 20.0.0-next.0 | 20.3.16 |
| `@angular/core` | npm | From 20.0.0-next.0 | 20.3.16 |
| `@angular/core` | npm | From 21.0.0-next.0 | 21.0.7 |
| `@angular/core` | npm | From 21.0.0-next.0 | 21.0.7 |
| `@angular/core` | npm | From 21.1.0-next.0 | 21.1.0-rc.0 |
| `@angular/core` | npm | From 21.1.0-next.0 | 21.1.0-rc.0 |

Products: Angular Angular.

## How do I fix CVE-2026-22610?

Upgrade @angular/compiler to a fixed version for your release line: 19.2.18, 20.3.16, 21.0.7 or 21.1.0-rc.0.

## Is CVE-2026-22610 being exploited?

There is no known exploitation of CVE-2026-22610 in the wild and no public exploit code.

Public exploit code:

- https://github.com/ashizZz/CVE-2026-22610 (github_poc): https://github.com/ashizZz/CVE-2026-22610

## Other vulnerabilities in angular

- [CVE-2026-68945](https://insights.sbomify.com/CVE-2026-68945/): Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (high 8.8)
- [CVE-2026-46417](https://insights.sbomify.com/CVE-2026-46417/): Angular: SSRF via Hostname Hijacking in @angular/platform-server (high 8.8)
- [CVE-2026-50168](https://insights.sbomify.com/CVE-2026-50168/): Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass (high 8.8)
- [CVE-2026-54266](https://insights.sbomify.com/CVE-2026-54266/): Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning (high 8.8)
- [CVE-2026-41423](https://insights.sbomify.com/CVE-2026-41423/): Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22610 and fix it if it is affected.

What it is: CVE-2026-22610 is a high-severity cross-site scripting vulnerability in angular, published on 10 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22610 in the wild and no public exploit code.

Affected packages and fixed versions:
- @angular/compiler (npm): affected all versions up to 18.2.14; no fix listed
- @angular/compiler (npm): affected all versions up to 18.2.14; no fix listed
- @angular/compiler (npm): affected from 19.0.0-next.0; fixed in 19.2.18
- @angular/compiler (npm): affected from 19.0.0-next.0; fixed in 19.2.18
- @angular/compiler (npm): affected from 20.0.0-next.0; fixed in 20.3.16
- @angular/compiler (npm): affected from 20.0.0-next.0; fixed in 20.3.16
- @angular/compiler (npm): affected from 21.0.0-next.0; fixed in 21.0.7
- @angular/compiler (npm): affected from 21.0.0-next.0; fixed in 21.0.7
- @angular/compiler (npm): affected from 21.1.0-next.0; fixed in 21.1.0-rc.0
- @angular/compiler (npm): affected from 21.1.0-next.0; fixed in 21.1.0-rc.0
- @angular/core (npm): affected all versions up to 18.2.14; no fix listed
- @angular/core (npm): affected all versions up to 18.2.14; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22610/ (Markdown: https://insights.sbomify.com/CVE-2026-22610/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22610
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22610
- OSV: https://osv.dev/vulnerability/CVE-2026-22610

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22610/
Summaries are generated and may contain mistakes; the official description above is the record.