Advisory

GHSA-692r-grfm-v8x7

Also known as: CVE-2026-52725

Summary

@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-15 16:51 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

@angular/core

npm · All systems

Affected

  • introduced 21.0.0-next.0, fixed 21.2.15 (semver)

Fixed versions

21.2.15

Fix

@angular/core

npm · All systems

Affected

  • introduced 22.0.0-next.0, fixed 22.0.0-rc.2 (semver)

Fixed versions

22.0.0-rc.2

Fix

@angular/core

npm · All systems

Affected

  • introduced 19.0.0-next.0, fixed 19.2.23 (semver)

Fixed versions

19.2.23

Fix

@angular/core

npm · All systems

Affected

  • introduced 0, last affected 18.2.14 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

@angular/core

npm · All systems

Affected

  • introduced 20.0.0-next.0, fixed 20.3.22 (semver)

Fixed versions

20.3.22

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences