CVE-2026-54265: Angular: Two-Way Property Binding Sanitization Bypass (XSS)

Published Jun 15, 2026
·
Updated

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).

Impact Any Angular application that uses two-way data binding ([()] or bindon-) on security-sensitive native DOM properties (like innerHTML, href on <a>, src on <img>/<iframe>, etc.) is vulnerable to this security bypass.

Once exploited, this allows a malicious actor to supply an unsanitized property binding value that bypasses core sanitization constraints. This could lead to the execution of arbitrary JavaScript within the target user's browser context, potentially resulting in session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.

Attack Preconditions To successfully exploit this vulnerability, the following environment parameters and application states must concurrently exist: 1. Two-Way Binding on Sensitive Properties: The application must bind to a sensitive native DOM property using the two-way binding syntax (e.g., <div [(innerHTML)]="userContent"></div>). 2. User-Controlled Input: The value bound to this property must be influenceable by user-controlled input. 3. Absence of Additional Sanitization: The application does not perform separate manual sanitization (e.g., via DomSanitizer) before passing the value to the bound property.

Patches 22.0.1 21.2.17 20.3.25

Other sources

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.

MITRE

Affected Software

8 affected componentsFixes available
npm/@angular/compiler<=19.2.25
npm/@angular/compiler>=20.0.0-next.0<20.3.25
20.3.25
npm/@angular/compiler>=21.0.0-next.0<21.2.17
21.2.17
npm/@angular/compiler>=22.0.0-next.0<22.0.1
22.0.1
angular Angular Node.js<=19.2.25
angular Angular Node.js>=20.0.0<20.3.25
angular Angular Node.js>=21.0.0<21.2.17
angular Angular Node.js>=22.0.0<22.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@angular/compiler to a version that resolves this vulnerability.

    Fixed in 20.3.25
  2. Upgrade

    Upgrade npm/@angular/compiler to a version that resolves this vulnerability.

    Fixed in 21.2.17
  3. Upgrade

    Upgrade npm/@angular/compiler to a version that resolves this vulnerability.

    Fixed in 22.0.1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20.3.25
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 21.2.17
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 22.0.1

Event History

Jun 15, 2026
Advisory Published
via GitHub·05:22 PM
Data Sourced
via GitHub·05:22 PM
DescriptionWeaknessAffected Software
Jun 22, 2026
CVE Published
via MITRE·03:27 PM
Data Sourced
via MITRE·03:27 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54265?

CVE-2026-54265 has a risk score of 55, indicating a moderate severity level.

2

What does CVE-2026-54265 exploit?

CVE-2026-54265 exploits a vulnerability in the @angular/compiler package that allows for bypassing DOM property sanitization.

3

How can I mitigate CVE-2026-54265?

Mitigation for CVE-2026-54265 involves avoiding the use of two-way bindings for properties that require sanitization.

4

Which versions of @angular/compiler are affected by CVE-2026-54265?

CVE-2026-54265 affects specific versions of the @angular/compiler package prior to the fix provided in newer releases.

5

What kind of attacks can CVE-2026-54265 facilitate?

CVE-2026-54265 can facilitate cross-site scripting (XSS) attacks if not properly managed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203