CVE-2026-54265

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

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.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Kodem intelligence

• 22.0.1
• 21.2.17
• 20.3.25

1. What is CVE-2026-54265? CVE-2026-54265 is a medium-severity cross-site scripting (XSS) vulnerability in @angular/compiler (npm), affecting versions >= 22.0.0-next.0, < 22.0.1. It is fixed in 22.0.1, 21.2.17, 20.3.25. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. Which versions of @angular/compiler are affected by CVE-2026-54265? @angular/compiler (npm) versions >= 22.0.0-next.0, < 22.0.1 is affected.
3. Is there a fix for CVE-2026-54265? Yes. CVE-2026-54265 is fixed in 22.0.1, 21.2.17, 20.3.25. Upgrade to this version or later.
4. Is CVE-2026-54265 exploitable, and should I be worried? Whether CVE-2026-54265 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-54265 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-54265?
   • Upgrade @angular/compiler to 22.0.1 or later
   • Upgrade @angular/compiler to 21.2.17 or later
   • Upgrade @angular/compiler to 20.3.25 or later