Answer in brief
CVE-2026-52725 records a Medium severity (CVSS 6.1) vulnerability in @angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS). The current sources do not mark it as known exploited. The current feed maps @angular/core (npm), @angular/core (npm), @angular/core (npm), @angular/core (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/core (npm), @angular/core (npm), @angular/core (npm), @angular/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @angular/corenpm | >=21.0.0-next.0,<21.2.15 | 21.2.15 |
| @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 | 19.2.23 |
| @angular/corenpm | >=20.0.0-next.0,<20.3.22 | 20.3.22 |
| @angular/corenpm | <=18.2.14 | Not reported |
| @angular/corenpm | >=21.0.0-next.0,<21.2.15 | 21.2.15 |
| @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 | 19.2.23 |
| @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 | >=19.0.0-next.0<19.2.22 | Not reported |
| @angular/corenpm | >=20.0.0-next.0,<20.3.22 | 20.3.22 |
| @angular/corenpm | <=18.2.14 | Not reported |
| @angular/corenpm | >=21.0.0-next.0<21.2.15 | Not reported |
Published upstream
May 28, 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/core` package allows bypassing script-execution restrictions during dynamic component creation. Specifically, the dynamic component instantiation mechanism (`createComponent`) failed to reject mounting components directly onto a `<script>` or namespaced script element (such as `<svg:script>`). This enabled the initialization of custom components on a tag that executes scripts, allowing attackers to hijack or inject script-executing hosts. This flaw enables an attacker who can control the host element or selector parameter passed to `createComponent` to initialize or mount an Angular component directly onto a `<script>` tag, leading to execution of untrusted code or client-side Cross-Site Scripting (XSS). ### Impact Any Angular application that registers dynamic components based on user-supplied parameters (like selectors or host elements) is vulnerable to this security bypass. Once exploited, this allows a malicious actor to mount a dynamic component on a script tag, bypassing core dynamic component creation safeguards 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 Host Selection:** The application must accept user-controlled inputs that are passed as a selector/host element to `createComponent`. 2. **Absence of Additional Context Sanitization:** The application does not perform separate input sanitization before feeding values to the dynamic creation APIs. ### Patches * 22.0.0-rc.2 * 21.2.15 * 20.3.22 * 19.2.23 ### References * https://github.com/angular/angular/pull/68686 * https://github.com/angular/angular/pull/68713
Quoted source text, attributed separately from HOL analysis.