@angular/core
Affected
- introduced
21.0.0-next.0, fixed21.2.15(semver)
Fixed versions
21.2.15
Fix
- Fixed version
21.2.15npm install @angular/[email protected]
Advisory
Also known as: 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., <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:
<svg:script>) to evade standard tag-name blocklists/checks.Patches
Medium Basis: The source's own band: MODERATE
21.0.0-next.0, fixed 21.2.15 (semver)21.2.15
21.2.15npm install @angular/[email protected]22.0.0-next.0, fixed 22.0.0-rc.2 (semver)22.0.0-rc.2
22.0.0-rc.2npm install @angular/[email protected]20.0.0-next.0, fixed 20.3.22 (semver)20.3.22
20.3.22npm install @angular/[email protected]19.0.0-next.0, fixed 19.2.22 (semver)19.2.22
19.2.22npm install @angular/[email protected]0, last affected 18.2.14 (semver)None listed
No fixed version is listed.
21.0.0-next.0, fixed 21.2.15 (semver)21.2.15
21.2.15npm install @angular/[email protected]22.0.0-next.0, fixed 22.0.0-rc.2 (semver)22.0.0-rc.2
22.0.0-rc.2npm install @angular/[email protected]20.0.0-next.0, fixed 20.3.22 (semver)20.3.22
20.3.22npm install @angular/[email protected]19.0.0-next.0, fixed 19.2.22 (semver)19.2.22
19.2.22npm install @angular/[email protected]0, last affected 18.2.14 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0