CVE-2026-50557: Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
An issue in the @angular/compiler and @angular/core packages allows bypassing element and attribute sanitization/validation through specific namespace workarounds. Specifically, namespaced script elements (e.g., or ) were not properly identified as script elements by the Angular template preparser, allowing them to pass through template compilation without being stripped.
Published Jun 15, 2026 · Updated Jul 15, 2026
Affected packages
@angular/core
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.15
- Fixed in
- 21.2.15
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.0-rc.2
- Fixed in
- 22.0.0-rc.2
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.22
- Fixed in
- 20.3.22
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.22
- Fixed in
- 19.2.22
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.15
- Fixed in
- 21.2.15
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.0-rc.2
- Fixed in
- 22.0.0-rc.2
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.22
- Fixed in
- 20.3.22
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.22
- Fixed in
- 19.2.22
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/compiler
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
An issue in the @angular/compiler and @angular/core packages allows bypassing element and attribute sanitization/validation through specific namespace workarounds.
Specifically, namespaced script elements (e.g., <svg:script> or <:svg:script>) were not properly identified as script elements by the Angular template preparser, allowing them to pass through template compilation without being stripped.
Furthermore, security context schema mappings for element attributes did not consistently handle attributes within namespaced elements (like SVG and MathML), opening up gaps where malicious namespaced attributes could bypass runtime and compile-time sanitizers.
Combined, these flaws enable an attacker who can inject or supply a template/tag structure with custom namespaces to bypass Angular's script-stripping logic and attribute sanitizers, leading to client-side Cross-Site Scripting (XSS).
Impact
Any Angular application that compiles user-controlled templates at runtime, or relies on sanitization of namespaced elements/attributes, is vulnerable to this security bypass.
Once exploited, this allows a malicious actor to inject a namespaced script element or dynamic attribute bindings, bypassing core sanitization constraints to execute arbitrary JavaScript within the target user's browser context. This could lead to session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.
Attack Preconditions
To successfully exploit these vulnerabilities, the following environment parameters and application states must all concurrently exist:
- User-Controlled Template Input: The application must accept user-controlled inputs that are directly processed by the Angular template compiler at runtime.
- Namespace Parsing Support: The input structure must employ custom namespace prefixes (such as
<svg:script>) to evade standard tag-name blocklists/checks. - Absence of Additional Context Sanitization: The application does not perform separate input sanitization before feeding values to the Angular compiler.
Patches
- 22.0.0-rc.2
- 21.2.15
- 20.3.22
- 19.2.23
Credited to SkyZeroZx, alan-agius4, josephperrott, AndrewKushnir.
References
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-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, 2026CVE-2026-32635
Angular vulnerable to XSS in i18n attribute bindings
high9.0No fixMar 13, 2026
