CVE-2026-52725: @angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
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 or namespaced script element (such as ).
Published Jun 15, 2026 · Updated Jul 15, 2026
Affected packages
@angular/core
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.15
- Fixed in
- 21.2.15
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.0-rc.2
- Fixed in
- 22.0.0-rc.2
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.22
- Fixed in
- 19.2.23
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.22
- Fixed in
- 20.3.22
- Check
npm ls @angular/core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- User-Controlled Host Selection: The application must accept user-controlled inputs that are passed as a selector/host element to
createComponent. - 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
Credited to SkyZeroZx, AndrewKushnir, alan-agius4, josephperrott.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-88057
Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
medium5.3No fixSep 10, 2026CVE-2026-69151
Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
high7.6No fixAug 3, 2026CVE-2026-50557
Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
medium6.1No fixJun 15, 2026CVE-2026-54267
Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
high6.1No fixJun 15, 2026CVE-2026-32635
Angular vulnerable to XSS in i18n attribute bindings
high9.0No fixMar 13, 2026CVE-2026-27970
Angular i18n vulnerable to Cross-Site Scripting
high6.1No fixFeb 27, 2026
