You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
OR
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions up to (including) 18.2.14
*cpe:2.3:a:angularjs:angularjs:22.0.0:next0:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next1:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next10:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next11:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next12:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next2:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next3:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next4:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next5:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next6:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next7:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next8:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next9:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:rc0:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:rc1:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 19.0.0 up to (excluding) 19.2.23
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 20.0.0 up to (excluding) 20.3.22
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 21.0.0 up to (excluding) 21.2.15
OR
*cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions up to (including) 19.2.25
*cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions from (including) 20.0.0 up to (excluding) 20.3.25
*cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions from (including) 21.0.0 up to (excluding) 21.2.17
*cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* versions from (including) 22.0.0 up to (excluding) 22.0.1
Initial Analysis by NIST6/26/2026 3:35:06 PM
Action
Type
Old Value
New Value
Added
CVSS V3.1
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Added
CPE Configuration
OR
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions up to (including) 18.2.14
*cpe:2.3:a:angularjs:angularjs:22.0.0:next0:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next1:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next10:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next11:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next12:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next2:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next3:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next4:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next5:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next6:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next7:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next8:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next9:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:rc0:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:rc1:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 19.0.0 up to (excluding) 19.2.23
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 20.0.0 up to (excluding) 20.3.22
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 21.0.0 up to (excluding) 21.2.15
New CVE Received from GitHub, Inc.6/22/2026 12:16:39 PM
Action
Type
Old Value
New Value
Added
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.