@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS) (CVE-2026-54265)
A vulnerability in the @angular/compiler package allows bypassing DOM property sanitization when using two-way property bindings on sensitive native DOM properties such as innerHTML, src, href, and others. This flaw occurs because the Angular template compiler fails to apply the required sanitizer function for two-way bindings, unlike one-way bindings which are properly sanitized. Exploiting this issue could enable an attacker controlling the bound value to execute arbitrary JavaScript in the user's browser, leading to potential session hijacking or data exposure. The vulnerability affects Angular versions up to 19.2.25 and is patched in versions 20.3.25, 21.2.17, and 22.0.1. Exploitation requires that the application uses two-way binding on sensitive properties with user-controllable input and lacks additional manual sanitization.
AI Analysis
Technical Summary
The @angular/compiler package contains a sanitization bypass vulnerability (CVE-2026-54265) related to two-way property bindings on native DOM properties that require sanitization (e.g., innerHTML, src, href). The Angular template compiler does not apply the appropriate sanitizer function for two-way bindings, allowing unsanitized values to be bound and potentially enabling client-side Cross-Site Scripting (XSS). This issue affects Angular versions <=19.2.25 and has been fixed in versions 20.3.25, 21.2.17, and 22.0.1. Successful exploitation requires that the application uses two-way binding syntax on sensitive properties with user-controlled input and no additional sanitization.
Potential Impact
Applications using vulnerable Angular versions that bind user-controllable input to sensitive DOM properties via two-way binding are at risk of client-side XSS attacks. This can lead to arbitrary JavaScript execution in the context of the user's browser, potentially resulting in session hijacking, exposure of sensitive information, or unauthorized actions performed on behalf of the user.
Mitigation Recommendations
Upgrade to one of the patched versions: 20.3.25, 21.2.17, or 22.0.1 of @angular/compiler. Until patched, avoid using two-way binding syntax on sensitive native DOM properties such as innerHTML, src, href, data, or sandbox, especially with user-controlled input. Alternatively, apply manual sanitization (e.g., via Angular's DomSanitizer) before binding values to these properties. Patch status is confirmed by the vendor advisory indicating fixed versions.
@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS) (CVE-2026-54265)
Description
A vulnerability in the @angular/compiler package allows bypassing DOM property sanitization when using two-way property bindings on sensitive native DOM properties such as innerHTML, src, href, and others. This flaw occurs because the Angular template compiler fails to apply the required sanitizer function for two-way bindings, unlike one-way bindings which are properly sanitized. Exploiting this issue could enable an attacker controlling the bound value to execute arbitrary JavaScript in the user's browser, leading to potential session hijacking or data exposure. The vulnerability affects Angular versions up to 19.2.25 and is patched in versions 20.3.25, 21.2.17, and 22.0.1. Exploitation requires that the application uses two-way binding on sensitive properties with user-controllable input and lacks additional manual sanitization.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @angular/compiler package contains a sanitization bypass vulnerability (CVE-2026-54265) related to two-way property bindings on native DOM properties that require sanitization (e.g., innerHTML, src, href). The Angular template compiler does not apply the appropriate sanitizer function for two-way bindings, allowing unsanitized values to be bound and potentially enabling client-side Cross-Site Scripting (XSS). This issue affects Angular versions <=19.2.25 and has been fixed in versions 20.3.25, 21.2.17, and 22.0.1. Successful exploitation requires that the application uses two-way binding syntax on sensitive properties with user-controlled input and no additional sanitization.
Potential Impact
Applications using vulnerable Angular versions that bind user-controllable input to sensitive DOM properties via two-way binding are at risk of client-side XSS attacks. This can lead to arbitrary JavaScript execution in the context of the user's browser, potentially resulting in session hijacking, exposure of sensitive information, or unauthorized actions performed on behalf of the user.
Mitigation Recommendations
Upgrade to one of the patched versions: 20.3.25, 21.2.17, or 22.0.1 of @angular/compiler. Until patched, avoid using two-way binding syntax on sensitive native DOM properties such as innerHTML, src, href, data, or sandbox, especially with user-controlled input. Alternatively, apply manual sanitization (e.g., via Angular's DomSanitizer) before binding values to these properties. Patch status is confirmed by the vendor advisory indicating fixed versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-58w9-8g37-x9v5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-54265"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a58b41268715ace43d68272
Added to database: 07/16/2026, 10:36:02 UTC
Last enriched: 07/16/2026, 10:54:27 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.