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 has XSS Vulnerability via Unsanitized SVG Script Attributes

CVSS 4.0 8.5 HIGHEUVD CVSS 4.0 8.5 CVSS 4.0 · [email protected] · Secondary 8.5 HIGHCVSS 3.1 · [email protected] · Primary 6.1 MEDIUMCVSS_V4 Publisher rating HIGHFixed by @angular/compiler 21.1.0-rc.0Fixed by @angular/core 21.1.0-rc.0Fixed by @angular/compiler 21.0.7Fixed by @angular/core 21.0.7KEV status unknown

cve-program · CVE-2026-22610

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.

Read the publisher's advisory

euvd · EUVD-2026-1698

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.

Read the publisher's advisory

nvd · CVE-2026-22610

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.

Read the publisher's advisory

osv · GHSA-jrmj-c5cx-3cw6

Published

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the `href` and `xlink:href` attributes of SVG `<script>` elements as a **Resource URL** context. In a standard security model, attributes that can load and execute code (like a script's source) should be strictly validated. However, because the compiler does not classify these specific SVG attributes correctly, it allows attackers to bypass Angular's built-in security protections. When template binding is used to assign user-controlled data to these attributes for example, `<script [attr.href]="userInput">` the compiler treats the value as a standard string or a non-sensitive URL rather than a resource link. This enables an attacker to provide a malicious payload, such as a `data:text/javascript` URI or a link to an external malicious script. ### Impact When successfully exploited, this vulnerability allows for **arbitrary JavaScript execution** within the context of the victim's browser session. This can lead to: - **Session Hijacking:** Stealing session cookies, localStorage data, or authentication tokens. - **Data Exfiltration:** Accessing and transmitting sensitive information displayed within the application. - **Unauthorized Actions:** Performing state-changing actions (like clicking buttons or submitting forms) on behalf of the authenticated user. ### Attack Preconditions 1. The victim application must explicitly use SVG `<script>` elements within its templates. 2. The application must use property or attribute binding (interpolation) for the `href` or `xlink:href` attributes of those SVG scripts. 3. The data bound to these attributes must be derived from an untrusted source (e.g., URL parameters, user-submitted database entries, or unsanitized API responses). ### Patches - 19.2.18 - 20.3.16 - 21.0.7 - 21.1.0-rc.0 ### Workarounds Until the patch is applied, developers should: - **Avoid Dynamic Bindings**: Do not use Angular template binding (e.g., `[attr.href]`) for SVG `<script>` elements. - **Input Validation**: If dynamic values must be used, strictly validate the input against a strict allowlist of trusted URLs on the server side or before it reaches the template. ### Resources - https://github.com/angular/angular/pull/66318

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-22610

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": ">= 21.1.0-next.0, < 21.1.0-rc.0",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0, < 21.0.7",
                            "status": "affected"
                        },
                        {
                            "version": ">= 20.0.0-next.0, < 20.3.16",
                            "status": "affected"
                        },
                        {
                            "version": "< 19.2.18",
                            "status": "affected"
                        }
                    ]
                }

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

euvd · EUVD-2026-1698

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: Jan 10, 2026, 3:35:40 AM

dateUpdated: Jun 2, 2026, 1:00:45 PM

9 related source bulletins · separate from aliases

ICSA-26-071-03: Siemens SIDIS Prime

CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62522 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610

WID-SEC-W-2026-0778: Dell Secure Connect Gateway Policy Manager: Mehrere Schwachstellen

CVE-2014-8991 · CVE-2015-2296 · CVE-2019-6778 · CVE-2020-10756 · CVE-2020-13645 · CVE-2020-1983 · CVE-2020-24455 · CVE-2020-25219 · CVE-2020-26154 · CVE-2020-29130 · CVE-2021-3592 · CVE-2021-3593 · CVE-2021-3594 · CVE-2021-3595 · CVE-2022-40897 · CVE-2023-22745 · CVE-2023-5752 · CVE-2024-25621 · CVE-2024-29040 · CVE-2024-6345 · CVE-2025-10911 · CVE-2025-11226 · CVE-2025-11468 · CVE-2025-11563 · CVE-2025-11731 · CVE-2025-12084 · CVE-2025-12781 · CVE-2025-1352 · CVE-2025-13601 · CVE-2025-1372 · CVE-2025-1376 · CVE-2025-1377 · CVE-2025-13836 · CVE-2025-13837 · CVE-2025-14087 · CVE-2025-14512 · CVE-2025-15281 · CVE-2025-15282 · CVE-2025-15366 · CVE-2025-15367 · CVE-2025-15467 · CVE-2025-24294 · CVE-2025-28162 · CVE-2025-28164 · CVE-2025-31133 · CVE-2025-3576 · CVE-2025-47273 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-53057 · CVE-2025-53666 · CVE-2025-54770 · CVE-2025-54771 · CVE-2025-54798 · CVE-2025-55752 · CVE-2025-59375 · CVE-2025-6075 · CVE-2025-61661 · CVE-2025-61662 · CVE-2025-61663 · CVE-2025-61664 · CVE-2025-61748 · CVE-2025-61795 · CVE-2025-61984 · CVE-2025-61985 · CVE-2025-64329 · CVE-2025-64505 · CVE-2025-64506 · CVE-2025-64720 · CVE-2025-64756 · CVE-2025-65018 · CVE-2025-66035 · CVE-2025-66293 · CVE-2025-66412 · CVE-2025-66614 · CVE-2025-67721 · CVE-2025-68160 · CVE-2025-68973 · CVE-2025-69418 · CVE-2025-69419 · CVE-2025-69420 · CVE-2025-69421 · CVE-2025-69873 · CVE-2025-7039 · CVE-2025-8291 · CVE-2025-9187 · CVE-2025-9820 · CVE-2026-0672 · CVE-2026-0861 · CVE-2026-0865 · CVE-2026-0915 · CVE-2026-0988 · CVE-2026-1484 · CVE-2026-1485 · CVE-2026-1489 · CVE-2026-22610 · CVE-2026-22695 · CVE-2026-22795 · CVE-2026-22796 · CVE-2026-22801 · CVE-2026-24734 · CVE-2026-24882 · CVE-2026-25646

RHSA-2026:36882: Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes v2.14.3 security update

CVE-2025-13465 · CVE-2025-47907 · CVE-2025-48431 · CVE-2025-61726 · CVE-2025-61728 · CVE-2025-61729 · CVE-2025-62718 · CVE-2026-22029 · CVE-2026-22610 · CVE-2026-25639 · CVE-2026-25681 · CVE-2026-29063 · CVE-2026-32285 · CVE-2026-33186 · CVE-2026-33487 · CVE-2026-40175 · CVE-2026-40293 · CVE-2026-40895 · CVE-2026-41602 · CVE-2026-41603 · CVE-2026-41604 · CVE-2026-41605 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42039 · CVE-2026-42041 · CVE-2026-42043 · CVE-2026-42044 · CVE-2026-43869 · CVE-2026-43870 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44990

RHSA-2026:86618: Red Hat Security Advisory: New container image: rhceph-9.2

CVE-2023-46159 · CVE-2024-47866 · CVE-2024-48916 · CVE-2024-55565 · CVE-2025-12816 · CVE-2025-15599 · CVE-2025-26791 · CVE-2025-30156 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-58754 · CVE-2025-59343 · CVE-2025-62718 · CVE-2025-66030 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69873 · CVE-2026-0540 · CVE-2026-21441 · CVE-2026-22610 · CVE-2026-25639 · CVE-2026-26996 · CVE-2026-27903 · CVE-2026-27904 · CVE-2026-27970 · CVE-2026-32141 · CVE-2026-33228 · CVE-2026-33671 · CVE-2026-33672 · CVE-2026-33891 · CVE-2026-33894 · CVE-2026-33895 · CVE-2026-33896 · CVE-2026-39865 · CVE-2026-40175 · CVE-2026-40895 · CVE-2026-41238 · CVE-2026-41239 · CVE-2026-41240 · CVE-2026-41305 · CVE-2026-42033 · CVE-2026-42034 · CVE-2026-42035 · CVE-2026-42036 · CVE-2026-42037 · CVE-2026-42038 · CVE-2026-42039 · CVE-2026-42040 · CVE-2026-42041 · CVE-2026-42042 · CVE-2026-42043 · CVE-2026-42044 · CVE-2026-50152 · CVE-2026-58224

WID-SEC-W-2026-0063: Angular: Schwachstelle ermöglicht Cross-Site Scripting

CVE-2026-22610

SSA-485750: SSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800

CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62522 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610

ICSA-26-188-05: Siemens SINEC OS

CVE-2025-1352 · CVE-2025-1376 · CVE-2025-6052 · CVE-2025-6141 · CVE-2025-6170 · CVE-2025-7039 · CVE-2025-8732 · CVE-2025-9086 · CVE-2025-9230 · CVE-2025-9231 · CVE-2025-9232 · CVE-2025-10966 · CVE-2025-13465 · CVE-2025-13601 · CVE-2025-39913 · CVE-2025-40214 · CVE-2025-40248 · CVE-2025-40250 · CVE-2025-40251 · CVE-2025-40252 · CVE-2025-40254 · CVE-2025-40257 · CVE-2025-40258 · CVE-2025-40261 · CVE-2025-40262 · CVE-2025-40263 · CVE-2025-40264 · CVE-2025-40271 · CVE-2025-40278 · CVE-2025-40280 · CVE-2025-40281 · CVE-2025-40345 · CVE-2025-46394 · CVE-2025-49794 · CVE-2025-49795 · CVE-2025-49796 · CVE-2025-60876 · CVE-2025-66035 · CVE-2025-66382 · CVE-2025-66412 · CVE-2025-69720 · CVE-2025-71185 · CVE-2025-71186 · CVE-2025-71188 · CVE-2025-71189 · CVE-2025-71190 · CVE-2025-71191 · CVE-2026-1484 · CVE-2026-1489 · CVE-2026-3784 · CVE-2026-22610 · CVE-2026-22976 · CVE-2026-22977 · CVE-2026-23025 · CVE-2026-23026 · CVE-2026-23030 · CVE-2026-23031 · CVE-2026-23032 · CVE-2026-23033 · CVE-2026-23037 · CVE-2026-23038 · CVE-2026-23111 · CVE-2026-23112 · CVE-2026-23220 · CVE-2026-23222 · CVE-2026-23228 · CVE-2026-23229 · CVE-2026-23230 · CVE-2026-23231 · CVE-2026-23236 · CVE-2026-23238 · CVE-2026-24515 · CVE-2026-25210 · CVE-2026-26157 · CVE-2026-26158 · CVE-2026-35535 · CVE-2026-41918

NCSC-2026-0079: Kwetsbaarheden verholpen in Siemens producten

CVE-2024-29857 · CVE-2024-30171 · CVE-2024-30172 · CVE-2024-41996 · CVE-2025-6965 · CVE-2025-7783 · CVE-2025-9230 · CVE-2025-9232 · CVE-2025-9670 · CVE-2025-12816 · CVE-2025-15284 · CVE-2025-27769 · CVE-2025-40943 · CVE-2025-55018 · CVE-2025-58751 · CVE-2025-58752 · CVE-2025-58754 · CVE-2025-62439 · CVE-2025-62522 · CVE-2025-64157 · CVE-2025-64718 · CVE-2025-64756 · CVE-2025-66030 · CVE-2025-66031 · CVE-2025-66035 · CVE-2025-66412 · CVE-2025-69277 · CVE-2026-22610 · CVE-2026-24858 · CVE-2026-25569 · CVE-2026-25570 · CVE-2026-25571 · CVE-2026-25572 · CVE-2026-25573 · CVE-2026-25605

SSA-253495: SSA-253495: Multiple Vulnerabilities in SINEC OS before V4.0

CVE-2025-1352 · CVE-2025-1376 · CVE-2025-6052 · CVE-2025-6141 · CVE-2025-6170 · CVE-2025-7039 · CVE-2025-8732 · CVE-2025-9086 · CVE-2025-9230 · CVE-2025-9231 · CVE-2025-9232 · CVE-2025-10966 · CVE-2025-13465 · CVE-2025-13601 · CVE-2025-39913 · CVE-2025-40214 · CVE-2025-40248 · CVE-2025-40250 · CVE-2025-40251 · CVE-2025-40252 · CVE-2025-40254 · CVE-2025-40257 · CVE-2025-40258 · CVE-2025-40261 · CVE-2025-40262 · CVE-2025-40263 · CVE-2025-40264 · CVE-2025-40271 · CVE-2025-40278 · CVE-2025-40280 · CVE-2025-40281 · CVE-2025-40345 · CVE-2025-46394 · CVE-2025-49794 · CVE-2025-49795 · CVE-2025-49796 · CVE-2025-60876 · CVE-2025-66035 · CVE-2025-66382 · CVE-2025-66412 · CVE-2025-69720 · CVE-2025-71185 · CVE-2025-71186 · CVE-2025-71188 · CVE-2025-71189 · CVE-2025-71190 · CVE-2025-71191 · CVE-2026-1484 · CVE-2026-1489 · CVE-2026-3784 · CVE-2026-22610 · CVE-2026-22976 · CVE-2026-22977 · CVE-2026-23025 · CVE-2026-23026 · CVE-2026-23030 · CVE-2026-23031 · CVE-2026-23032 · CVE-2026-23033 · CVE-2026-23037 · CVE-2026-23038 · CVE-2026-23111 · CVE-2026-23112 · CVE-2026-23220 · CVE-2026-23222 · CVE-2026-23228 · CVE-2026-23229 · CVE-2026-23230 · CVE-2026-23231 · CVE-2026-23236 · CVE-2026-23238 · CVE-2026-24515 · CVE-2026-25210 · CVE-2026-26157 · CVE-2026-26158 · CVE-2026-35535 · CVE-2026-41918

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-22610

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: Modified

Weakness classifications: CWE-79

Original publisher date fields

published: 2026-01-10T04:16:01.517

lastModified: 2026-06-17T10:20:09.593

6 source CPE criteria · context only
  • cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:21.1.0:next0:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:21.1.0:next1:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:21.1.0:next2:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:21.1.0:next3:*:*:*:node.js:*:*
  • cpe:2.3:a:angular:angular:21.1.0:next4:*:*:*: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-jrmj-c5cx-3cw6

Published

@angular/compiler

npm

SEMVER · introduced 21.1.0-next.0 → fixed 21.1.0-rc.0

@angular/core

npm

SEMVER · introduced 21.1.0-next.0 → fixed 21.1.0-rc.0

@angular/compiler

npm

SEMVER · introduced 21.0.0-next.0 → fixed 21.0.7

@angular/core

npm

SEMVER · introduced 21.0.0-next.0 → fixed 21.0.7

@angular/compiler

npm

SEMVER · introduced 20.0.0-next.0 → fixed 20.3.16

@angular/core

npm

SEMVER · introduced 20.0.0-next.0 → fixed 20.3.16

@angular/compiler

npm

SEMVER · introduced 19.0.0-next.0 → fixed 19.2.18

@angular/core

npm

SEMVER · introduced 19.0.0-next.0 → fixed 19.2.18

@angular/compiler

npm

SEMVER · introduced 0 → last_affected 18.2.14

@angular/core

npm

SEMVER · introduced 0 → last_affected 18.2.14

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 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current