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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 6.1, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 1 product from angular organizations running these solutions should prioritize assessment and patching.
Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2026-06-22T16:16:38.050
2026-07-09T15:40:45.797
Analyzed
CVSSv3.1: 6.1 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | angular | angular | ≤ 18.2.14 | Yes |
| Application | angular | angular | < 19.2.22 | Yes |
| Application | angular | angular | < 20.3.22 | Yes |
| Application | angular | angular | < 21.2.15 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
| Application | angular | angular | 22.0.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For angular's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.