Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

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

CVE-2026-54265GHSA-58w9-8g37-x9v5

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @angular/compiler

    Affected
    >= 22.0.0-next.0, < 22.0.1>= 21.0.0-next.0, < 21.2.17>= 20.0.0-next.0, < 20.3.25<= 19.2.25
    Fixed in
    20.3.25, 22.0.1, 21.2.17

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · 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 · score source
EPSS
  • CVE-2026-54265: 0.34% estimated exploitation activity in the next 30 days; percentile 27.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-58w9-8g37-x9v5

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-58w9-8g37-x9v5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54265

Advisory: @angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)
IDs: CVE-2026-54265, GHSA-58w9-8g37-x9v5
Record: https://patchnext.com/advisories/cve-2026-54265 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @angular/compiler 22.0.1, 21.2.17, 20.3.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @angular/compiler: affected >= 22.0.0-next.0, < 22.0.1; >= 21.0.0-next.0, < 21.2.17; >= 20.0.0-next.0, < 20.3.25; <= 19.2.25; fixed in 20.3.25, 22.0.1, 21.2.17

## Suggested inspection (read-only)
- `npm ls @angular/compiler --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @angular/compiler.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-58w9-8g37-x9v5 (OSV record GHSA-58w9-8g37-x9v5 lists affected ranges: npm @angular/compiler >=22.0.0-next.0 =21.0.0-next.0 =20.0.0-next.0 =0 <=19.2.25)
- Verified: https://github.com/advisories/GHSA-58w9-8g37-x9v5 (GitHub-reviewed advisory GHSA-58w9-8g37-x9v5 lists affected ranges: npm @angular/compiler >=22.0.0-next.0 =21.0.0-next.0 =20.0.0-next.0 =0 <=19.2.25)

Commands are suggestions: review each one before running it.

Loading voting…