Advisory

GHSA-58w9-8g37-x9v5

Also known as: CVE-2026-54265

Summary

@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-15 17:22 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

@angular/compiler

npm · All systems

Affected

  • introduced 22.0.0-next.0, fixed 22.0.1 (semver)

Fixed versions

22.0.1

Fix

@angular/compiler

npm · All systems

Affected

  • introduced 21.0.0-next.0, fixed 21.2.17 (semver)

Fixed versions

21.2.17

Fix

@angular/compiler

npm · All systems

Affected

  • introduced 20.0.0-next.0, fixed 20.3.25 (semver)

Fixed versions

20.3.25

Fix

@angular/compiler

npm · All systems

Affected

  • introduced 0, last affected 19.2.25 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences