Answer in brief
CVE-2026-50557 records a Medium severity (CVSS 6.1) vulnerability in Angular: Template and Attribute Namespace Sanitization Bypass (XSS). The current sources do not mark it as known exploited. The current feed maps @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @angular/compilernpm | >=22.0.0-next.0,<22.0.0-rc.2 | 22.0.0-rc.2 |
| @angular/compilernpm | >=19.0.0-next.0,<19.2.22 | 19.2.22 |
| @angular/compilernpm | <=18.2.14 | Not reported |
| @angular/compilernpm | >=20.0.0-next.0,<20.3.22 | 20.3.22 |
| @angular/compilernpm | >=21.0.0-next.0,<21.2.15 | 21.2.15 |
| @angular/compilernpm | >=22.0.0-next.0,<22.0.0-rc.2 | 22.0.0-rc.2 |
| @angular/compilernpm | >=19.0.0-next.0,<19.2.22 | 19.2.22 |
| @angular/compilernpm | <=18.2.14 | Not reported |
| @angular/compilernpm | >=20.0.0-next.0,<20.3.22 | 20.3.22 |
| @angular/compilernpm | >=21.0.0-next.0<21.2.15 | Not reported |
| @angular/compilernpm | >=22.0.0-next.0<22.0.0-rc.2 | Not reported |
| @angular/compilernpm | >=20.0.0-next.0<20.3.22 | Not reported |
| @angular/compilernpm | >=19.0.0-next.0<19.2.22 | Not reported |
| @angular/compilernpm | >=21.0.0-next.0,<21.2.15 | 21.2.15 |
| @angular/corenpm | >=20.0.0-next.0,<20.3.22 | 20.3.22 |
| @angular/corenpm | >=19.0.0-next.0,<19.2.22 | 19.2.22 |
| @angular/corenpm | <=18.2.14 | Not reported |
| @angular/corenpm | >=22.0.0-next.0,<22.0.0-rc.2 | 22.0.0-rc.2 |
| @angular/corenpm | >=21.0.0-next.0,<21.2.15 | 21.2.15 |
| @angular/corenpm | >=20.0.0-next.0,<20.3.22 | 20.3.22 |
| @angular/corenpm | >=19.0.0-next.0,<19.2.22 | 19.2.22 |
| @angular/corenpm | <=18.2.14 | Not reported |
| @angular/corenpm | >=21.0.0-next.0<21.2.15 | Not reported |
| @angular/corenpm | >=22.0.0-next.0<22.0.0-rc.2 | Not reported |
| @angular/corenpm | >=20.0.0-next.0<20.3.22 | Not reported |
| @angular/corenpm | >=22.0.0-next.0,<22.0.0-rc.2 | 22.0.0-rc.2 |
| @angular/corenpm | >=19.0.0-next.0<19.2.22 | Not reported |
| @angular/corenpm | >=21.0.0-next.0,<21.2.15 | 21.2.15 |
Published upstream
Jun 5, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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: 1. **User-Controlled Template Input:** The application must accept user-controlled inputs that are directly processed by the Angular template compiler at runtime. 2. **Namespace Parsing Support:** The input structure must employ custom namespace prefixes (such as `<svg:script>`) to evade standard tag-name blocklists/checks. 3. **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 ### References * https://github.com/angular/angular/pull/68868 * https://github.com/angular/angular/pull/68689
Quoted source text, attributed separately from HOL analysis.