# CVE-2026-50557: Angular: Template and Attribute Namespace Sanitization Bypass (XSS) > Attackers can bypass Angular's sanitization using namespaced elements to execute arbitrary JavaScript in the victim's browser. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Jun 2026 - **Updated:** 22 Jun 2026 - **Also known as:** DEBIAN-CVE-2026-50557, GHSA-f3m7-gqxr-g87x, UBUNTU-CVE-2026-50557 ## What is CVE-2026-50557? CVE-2026-50557 is a medium-severity cross-site scripting vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, 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 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.2.22, 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 <: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). This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.2.22. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2026-50557? 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.22 | | `@angular/compiler` | npm | From 19.0.0-next.0 | 19.2.22 | | `@angular/compiler` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/compiler` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/compiler` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/compiler` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/compiler` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | | `@angular/compiler` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | | `@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.22 | | `@angular/core` | npm | From 19.0.0-next.0 | 19.2.22 | | `@angular/core` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/core` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/core` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/core` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/core` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | | `@angular/core` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | Products: Angular Angular. ## How do I fix CVE-2026-50557? Upgrade @angular/compiler to a fixed version for your release line: 19.2.22, 20.3.22, 21.2.15 or 22.0.0-rc.2. ## Is CVE-2026-50557 being exploited? There is no known exploitation of CVE-2026-50557 in the wild and no public exploit code. ## 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-50557 and fix it if it is affected. What it is: CVE-2026-50557 is a medium-severity cross-site scripting vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-50557 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.22 - @angular/compiler (npm): affected from 19.0.0-next.0; fixed in 19.2.22 - @angular/compiler (npm): affected from 20.0.0-next.0; fixed in 20.3.22 - @angular/compiler (npm): affected from 20.0.0-next.0; fixed in 20.3.22 - @angular/compiler (npm): affected from 21.0.0-next.0; fixed in 21.2.15 - @angular/compiler (npm): affected from 21.0.0-next.0; fixed in 21.2.15 - @angular/compiler (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2 - @angular/compiler (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2 - @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-50557/ (Markdown: https://insights.sbomify.com/CVE-2026-50557/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50557 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50557 - OSV: https://osv.dev/vulnerability/CVE-2026-50557 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-50557/ Summaries are generated and may contain mistakes; the official description above is the record.