Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)

CVSS 4.0 5.3 MEDIUMEUVD CVSS 4.0 5.3 CVSS 4.0 · [email protected] · Secondary 5.3 MEDIUMCVSS 3.1 · [email protected] · Primary 6.1 MEDIUMCVSS_V3 CVSS_V4 Publisher rating MODERATEFixed by @angular/core 21.2.15Fixed by @angular/core 22.0.0-rc.2Fixed by @angular/core 19.2.23Fixed by @angular/core 20.3.22KEV status unknown

cve-program · CVE-2026-52725

Published

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

Read the publisher's advisory

euvd · EUVD-2026-38261

Published

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

Read the publisher's advisory

nvd · CVE-2026-52725

Published

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

Read the publisher's advisory

osv · GHSA-692r-grfm-v8x7

Published

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

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-52725

Published

angular

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "angular",
                    "product": "angular",
                    "versions": [
                        {
                            "version": ">= 22.0.0-next.0 < 22.0.0-rc.2",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0 < 21.2.15",
                            "status": "affected"
                        },
                        {
                            "version": ">= 20.0.0-next.0 < 20.3.22",
                            "status": "affected"
                        },
                        {
                            "version": ">= 19.0.0-next.0 < 19.2.22",
                            "status": "affected"
                        },
                        {
                            "version": "<= 18.2.14",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-38261

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jun 22, 2026, 3:18:43 PM

dateUpdated: Jun 22, 2026, 3:59:33 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-52725

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-79

Original publisher date fields

published: 2026-06-22T16:16:38.193

lastModified: 2026-07-09T15:38:38.650

16 source CPE criteria · context only
  • cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next0:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next1:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next10:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next11:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next12:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next2:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next3:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next4:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next5:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next6:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next7:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next8:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:next9:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:22.0.0:rc1:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-692r-grfm-v8x7

Published

@angular/core

npm

SEMVER · introduced 21.0.0-next.0 → fixed 21.2.15

@angular/core

npm

SEMVER · introduced 22.0.0-next.0 → fixed 22.0.0-rc.2

@angular/core

npm

SEMVER · introduced 19.0.0-next.0 → fixed 19.2.23

@angular/core

npm

SEMVER · introduced 0 → last_affected 18.2.14

@angular/core

npm

SEMVER · introduced 20.0.0-next.0 → fixed 20.3.22

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current