CVE-2026-54265 Angular: Two-Way Property Binding Sanitization Bypass (XSS)
Attackers can bypass Angular's DOM sanitization via two-way property bindings to execute arbitrary JavaScript, leading to Cross-Site Scripting.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-54265?
CVE-2026-54265 is a medium-severity cross-site scripting vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-54265?
8 open source packages ship an affected version, including @angular/compiler. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@angular/compiler npm | All versions to 19.2.25 | None |
@angular/compiler npm | All versions to 19.2.25 | None |
@angular/compiler npm | From 20.0.0-next.0 | 20.3.25 |
@angular/compiler npm | From 20.0.0-next.0 | 20.3.25 |
@angular/compiler npm | From 21.0.0-next.0 | 21.2.17 |
@angular/compiler npm | From 21.0.0-next.0 | 21.2.17 |
2 more packages
@angular/compiler npm | From 22.0.0-next.0 | 22.0.1 |
@angular/compiler npm | From 22.0.0-next.0 | 22.0.1 |
Products include Angular Angular.
How do I fix CVE-2026-54265?
Upgrade @angular/compiler to a fixed version for your release line: 20.3.25, 21.2.17 or 22.0.1.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-54265 being exploited?
There is no known exploitation of CVE-2026-54265 in the wild and no public exploit code.
Other vulnerabilities in angular
- CVE-2026-68945 Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
- CVE-2026-46417 Angular: SSRF via Hostname Hijacking in @angular/platform-server
- CVE-2026-50168 Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass
- CVE-2026-54266 Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
- CVE-2026-41423 Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
Sources
Also known as DEBIAN-CVE-2026-54265, GHSA-58w9-8g37-x9v5, UBUNTU-CVE-2026-54265.