6.1
MEDIUM CVSS 3.1
CVE-2026-54265
Angular: Two-Way Property Binding Sanitization Bypass (XSS)
Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property bindings. Specifically, when a native DOM property that requires sanitization (such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)]="value" or bindon-innerHTML="value"), the Angular template compiler failed to apply the appropriate schema-derived sanitizer resolution to the TwoWayProperty operation. As a result, native two-way DOM bindings were emitted without the required sanitizer function, whereas equivalent one-way bindings would be properly sanitized. This flaw enables an attacker who can control the value of a two-way bound sensitive property to bypass Angular's built-in sanitization logic, potentially leading to client-side Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.

INFO

Published Date :

June 22, 2026, 4:16 p.m.

Last Modified :

July 9, 2026, 3:39 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-54265 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Angular angular
2 Angular angular_language_service
1 Angularjs angularjs
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 MEDIUM [email protected]
CVSS 4.0 MEDIUM [email protected]
Solution
Update Angular to a patched version to fix DOM property sanitization bypass and XSS risks.
  • Update to Angular version 22.0.1 or later.
  • Update to Angular version 21.2.17 or later.
  • Update to Angular version 20.3.25 or later.
Public PoC/Exploit Available at Github

CVE-2026-54265 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-54265.

URL Resource
https://github.com/angular/angular/commit/3c70270c96677c0dd33585f2afe8e187113e5fb4 Patch
https://github.com/angular/angular/pull/69107 Issue Tracking Patch
https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5 Third Party Advisory
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-54265 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-54265 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Config files for my GitHub profile.

config github-config

Updated: 3 weeks ago
1 stars 1 fork 1 watcher
Born at : Dec. 14, 2021, 4:37 a.m. This repo has been linked 9 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-54265 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-54265 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Reanalysis by [email protected]

    Jul. 09, 2026

    Action Type Old Value New Value
    Changed CPE Configuration OR *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions up to (including) 18.2.14 *cpe:2.3:a:angularjs:angularjs:22.0.0:next0:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next1:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next10:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next11:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next12:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next2:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next3:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next4:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next5:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next6:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next7:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next8:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next9:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:rc0:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:rc1:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 19.0.0 up to (excluding) 19.2.23 *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 20.0.0 up to (excluding) 20.3.22 *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 21.0.0 up to (excluding) 21.2.15 OR *cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions up to (including) 19.2.25 *cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions from (including) 20.0.0 up to (excluding) 20.3.25 *cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions from (including) 21.0.0 up to (excluding) 21.2.17 *cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions from (including) 22.0.0 up to (excluding) 22.0.1
  • Initial Analysis by [email protected]

    Jun. 26, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
    Added CPE Configuration OR *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions up to (including) 18.2.14 *cpe:2.3:a:angularjs:angularjs:22.0.0:next0:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next1:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next10:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next11:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next12:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next2:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next3:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next4:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next5:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next6:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next7:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next8:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:next9:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:rc0:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:22.0.0:rc1:*:*:*:*:*:* *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 19.0.0 up to (excluding) 19.2.23 *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 20.0.0 up to (excluding) 20.3.22 *cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 21.0.0 up to (excluding) 21.2.15
    Added Reference Type GitHub, Inc.: https://github.com/angular/angular/commit/3c70270c96677c0dd33585f2afe8e187113e5fb4 Types: Patch
    Added Reference Type GitHub, Inc.: https://github.com/angular/angular/pull/69107 Types: Issue Tracking, Patch
    Added Reference Type GitHub, Inc.: https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5 Types: Third Party Advisory
  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Jun. 22, 2026

    Action Type Old Value New Value
    Added SSVC {'id': 'CVE-2026-54265', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-06-22T15:54:52.170678Z'}
  • New CVE Received by [email protected]

    Jun. 22, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'angular', 'product': 'angular', 'versions': [{'status': 'affected', 'version': '>= 22.0.0-next.0 < 22.0.1'}, {'status': 'affected', 'version': '>= 21.0.0-next.0 < 21.2.17'}, {'status': 'affected', 'version': '>= 20.0.0-next.0 < 20.3.25'}, {'status': 'affected', 'version': '<= 19.2.25'}]}]
    Added Description Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property bindings. Specifically, when a native DOM property that requires sanitization (such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)]="value" or bindon-innerHTML="value"), the Angular template compiler failed to apply the appropriate schema-derived sanitizer resolution to the TwoWayProperty operation. As a result, native two-way DOM bindings were emitted without the required sanitizer function, whereas equivalent one-way bindings would be properly sanitized. This flaw enables an attacker who can control the value of a two-way bound sensitive property to bypass Angular's built-in sanitization logic, potentially leading to client-side Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
    Added CVSS V4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    Added CWE CWE-79
    Added Reference https://github.com/angular/angular/commit/3c70270c96677c0dd33585f2afe8e187113e5fb4
    Added Reference https://github.com/angular/angular/pull/69107
    Added Reference https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.