Skip to content
VulniPulse
Sign in
Advisory severityMedium6.1Red Hat Linux

Medium [CVE-2026-54265] @angular/compiler: Angular: Two-Way Property Binding Sanitization Bypass (XSS)

This medium-severity Red Hat Linux advisory covers CVE-2026-54265 affecting Red Hat Advanced Cluster Management for Kubernetes 2, Red Hat build of Apicurio Registry 3.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-54265 Source published Source updated

VulniPulse record published Record updated

CVE-2026-54265
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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.

This vulnerability only affects Angular 2+ (versions 19.x through 22.x); AngularJS 1.x is a different codebase and is not affected. Red Hat products shipping AngularJS 1.x (such as firefox, grafana, and thunderbird) are not impacted by this flaw.

Is CVE-2026-54265 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-54265 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-54265?

Upgrade to a fixed release named by Red Hat:

  • 22.0.1
  • 21.2.17
  • 20.3.25

Confirm against the vendor advisory before you patch.

Affected versions
  • < 22.0.1
  • < 21.2.17
  • < 20.3.25

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • 22.0.1
  • 21.2.17
  • 20.3.25

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat

More Red Hat Linux advisories

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.