CVE-2026-22610: Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
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 elements as a Resource URL context. In a standard security model, attributes that can load and execute code (like a script's source) should be strictly validated.
Published Jan 9, 2026 · Updated Jun 9, 2026
Affected packages
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 21.1.0-next.0, < 21.1.0-rc.0
- Fixed in
- 21.1.0-rc.0
- Check
npm ls @angular/compiler
@angular/core
- Ecosystem
- npm
- Affected
- >= 21.1.0-next.0, < 21.1.0-rc.0
- Fixed in
- 21.1.0-rc.0
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.0.7
- Fixed in
- 21.0.7
- Check
npm ls @angular/compiler
@angular/core
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.0.7
- Fixed in
- 21.0.7
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.16
- Fixed in
- 20.3.16
- Check
npm ls @angular/compiler
@angular/core
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.16
- Fixed in
- 20.3.16
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.18
- Fixed in
- 19.2.18
- Check
npm ls @angular/compiler
@angular/core
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.18
- Fixed in
- 19.2.18
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/compiler
@angular/core
- Ecosystem
- npm
- Affected
- <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/core
Advisory details
From the GitHub Advisory Database (CC BY 4.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.
In a standard security model, attributes that can load and execute code (like a script's source) should be strictly validated. However, because the compiler does not classify these specific SVG attributes correctly, it allows attackers to bypass Angular's built-in security protections.
When template binding is used to assign user-controlled data to these attributes for example, <script [attr.href]="userInput"> the compiler treats the value as a standard string or a non-sensitive URL rather than a resource link. This enables an attacker to provide a malicious payload, such as a data:text/javascript URI or a link to an external malicious script.
Impact
When successfully exploited, this vulnerability allows for arbitrary JavaScript execution within the context of the victim's browser session. This can lead to:
- Session Hijacking: Stealing session cookies, localStorage data, or authentication tokens.
- Data Exfiltration: Accessing and transmitting sensitive information displayed within the application.
- Unauthorized Actions: Performing state-changing actions (like clicking buttons or submitting forms) on behalf of the authenticated user.
Attack Preconditions
- The victim application must explicitly use SVG
<script>elements within its templates. - The application must use property or attribute binding (interpolation) for the
hreforxlink:hrefattributes of those SVG scripts. - The data bound to these attributes must be derived from an untrusted source (e.g., URL parameters, user-submitted database entries, or unsanitized API responses).
Patches
- 19.2.18
- 20.3.16
- 21.0.7
- 21.1.0-rc.0
Workarounds
Until the patch is applied, developers should:
- Avoid Dynamic Bindings: Do not use Angular template binding (e.g.,
[attr.href]) for SVG<script>elements. - Input Validation: If dynamic values must be used, strictly validate the input against a strict allowlist of trusted URLs on the server side or before it reaches the template.
Resources
- https://github.com/angular/angular/pull/66318
Credited to alan-agius4, josephperrott, AndrewKushnir, jelbourn, hybrist, ShelbyKelley, gkalpak.
References
- https://github.com/angular/angular/security/advisories/GHSA-jrmj-c5cx-3cw6
- https://github.com/angular/angular/pull/66318
- https://nvd.nist.gov/vuln/detail/CVE-2026-22610
- https://github.com/angular/angular/commit/91dc91bae4a1bbefc58bef6ef739d0e02ab44d56
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://github.com/advisories/GHSA-jrmj-c5cx-3cw6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-88057
Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
medium5.3No fixSep 10, 2026CVE-2026-69151
Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
high7.6No fixAug 3, 2026CVE-2026-50557
Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
medium6.1No fixJun 15, 2026CVE-2026-52725
@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
medium6.1No fixJun 15, 2026CVE-2026-54265
@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)
medium6.1No fixJun 15, 2026CVE-2026-54267
Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
high6.1No fixJun 15, 2026
