Record summary

CVE-2026-50557 has a selected CVSS score of 5.3 (medium).

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., <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). This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22 and 19.2.22.

Description source: CVE List

Exploitation context

CISA SSVC decision

ExploitationNone
AutomatableYes
Technical impactPartial

CISA Coordinator · SSVC 2.0.3 · Evaluated Jun 22, 2026 · Source: CVE List

Affected products and versions

3
ProductSourceVersion rangeStatus
CVE List>= 21.0.0-next.0 < 21.2.15affected
>= 22.0.0-next.0 < 22.0.0-rc.2affected
>= 20.0.0-next.0 < 20.3.22affected
>= 19.0.0-next.0 < 19.2.22affected
<= 18.2.14affected
GitHub Advisory21.0.0-next.0 to < 21.2.15 · Fixed in 21.2.15affected
22.0.0-next.0 to < 22.0.0-rc.2 · Fixed in 22.0.0-rc.2affected
20.0.0-next.0 to < 20.3.22 · Fixed in 20.3.22affected
19.0.0-next.0 to < 19.2.22 · Fixed in 19.2.22affected
Through 18.2.14affected
GitHub Advisory21.0.0-next.0 to < 21.2.15 · Fixed in 21.2.15affected
22.0.0-next.0 to < 22.0.0-rc.2 · Fixed in 22.0.0-rc.2affected
20.0.0-next.0 to < 20.3.22 · Fixed in 20.3.22affected
19.0.0-next.0 to < 19.2.22 · Fixed in 19.2.22affected
Through 18.2.14affected

References

5