NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

CVE-2026-22610 — @angular/compiler

Fix: angular/angular@91dc91b

CVE-2026-22610 is a Cross-site Scripting (XSS) vulnerability in @angular/compiler. A fix is available for @angular/compiler — see the affected versions and patch details below.

Angular has XSS Vulnerability via Unsanitized SVG Script Attributes

Also known asGHSA-jrmj-c5cx-3cw6
Published
Updated
Affected
10 pkgs
Patched
8 / 10
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22610.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.32%0.64%0.96%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

10 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

12Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@angular/compilernpm
8.2Mdownloads / week
@angular/corenpm
8.4Mdownloads / week

Description

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

Affected Packages

10 total 8 fixed
EcosystemPackageVulnerable rangeFix
📦npm@angular/compiler≥ 21.1.0-next.0&&< 21.1.0-rc.021.1.0-rc.0npm install @angular/compiler@21.1.0-rc.0
📦npm@angular/core≥ 21.1.0-next.0&&< 21.1.0-rc.021.1.0-rc.0npm install @angular/core@21.1.0-rc.0
📦npm@angular/compiler≥ 21.0.0-next.0&&< 21.0.721.0.7npm install @angular/compiler@21.0.7
📦npm@angular/core≥ 21.0.0-next.0&&< 21.0.721.0.7npm install @angular/core@21.0.7
📦npm@angular/compiler≥ 20.0.0-next.0&&< 20.3.1620.3.16npm install @angular/compiler@20.3.16
📦npm@angular/core≥ 20.0.0-next.0&&< 20.3.1620.3.16npm install @angular/core@20.3.16

Affected Products

1 product · 9 configurations
Application
angularangular
≥ 21.0.0 && ≤ 18.2.14
1 version
21.1.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/compiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @angular/compiler to 21.1.0-rc.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22610 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated Moderate for Red Hat products. A cross-site scripting (XSS) flaw in the Angular Template Compiler allows an attacker to inject malicious scripts into web pages. This affects several Red Hat products, including Red Hat Enterprise Application Platform, Red Hat JBoss Fuse, Red Hat OpenStack…

Workaround published by Red Hat
This issue can be mitigating by avoiding the usage of dynamic bindings, this can be achieved by not using the Angular template binding `[attr.href]` when handling SVG `<script>` elements. If there's a need of using dynamic bindings, users are advised to validate the input against a strict list of trusted URLs on the server side before serving the values to the template.
Source: Red Hat security advisory for CVE-2026-22610 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Advanced Cluster Management for Kubernetes 2.14rhacm2/acm-grafana-rhel9:1782693386RHSA-2026:36882
Red Hat Ceph Storage 9.2rhceph/rhceph-9-rhel10:1790843527RHSA-2026:86618

Frequently Asked Questions

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 u
O3 Security · Impact-Aware SCA

Is CVE-2026-22610 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-22610: @angular/compiler — Fixed in 21.1.0-rc.0