Answer in brief
CVE-2026-88057 records a Medium severity (CVSS 0.0) vulnerability in Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler. The current sources do not mark it as known exploited. The current feed maps angular/angular (generic), @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps angular/angular (generic), @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| angular/angulargeneric | <=19.2.25 || >=20.0.0 <20.3.28 || >=21.0.0 <21.2.20 || >=22.0.0 <22.1.0 | 20.3.28, 21.2.20, 22.1.0 |
| @angular/compilernpm | >=21.0.0,<21.2.20 | 21.2.20 |
| @angular/compilernpm | >=22.0.0,<22.1.0 | 22.1.0 |
| @angular/compilernpm | >=20.0.0,<20.3.28 | 20.3.28 |
| @angular/compilernpm | <=19.2.25 | Not reported |
| @angular/compilernpm | >=21.0.0 <21.2.20 | 21.2.20 |
| @angular/compilernpm | >=20.0.0 <20.3.28 | 20.3.28 |
| @angular/compilernpm | >=0 | Not reported |
| @angular/compilernpm | >=21.0.0,<21.2.20 | 21.2.20 |
| @angular/compilernpm | >=22.0.0,<22.1.0 | 22.1.0 |
| @angular/compilernpm | >=20.0.0,<20.3.28 | 20.3.28 |
| @angular/compilernpm | <=19.2.25 | Not reported |
| @angular/compilernpm | >=22.0.0 <22.1.0 | 22.1.0 |
| @angular/corenpm | >=21.0.0,<21.2.20 | 21.2.20 |
| @angular/corenpm | >=22.0.0,<22.1.0 | 22.1.0 |
| @angular/corenpm | >=20.0.0,<20.3.28 | 20.3.28 |
| @angular/corenpm | <=19.2.25 | Not reported |
| @angular/corenpm | >=22.0.0 <22.1.0 | 22.1.0 |
| @angular/corenpm | >=21.0.0 <21.2.20 | 21.2.20 |
| @angular/corenpm | >=20.0.0 <20.3.28 | 20.3.28 |
| @angular/corenpm | >=0 | Not reported |
| @angular/corenpm | >=21.0.0,<21.2.20 | 21.2.20 |
| @angular/corenpm | >=22.0.0,<22.1.0 | 22.1.0 |
| @angular/corenpm | >=20.0.0,<20.3.28 | 20.3.28 |
| @angular/corenpm | <=19.2.25 | Not reported |
Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 25, 2026
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.0, Angular's compiler and runtime in @angular/core and @angular/compiler could omit or select an incorrect sanitizer for security-sensitive directive host bindings because SecurityContext was derived from the declaring directive or component selector rather than the concrete host element. The mismatch is reachable through hostDirectives composition, inherited HostBinding declarations, createComponent with a custom hostElement or dynamic directives, SVG/MathML namespace elements, and tag-neutral selectors such as :not(...). Attacker-controlled href, src, action, xlink:href, or data values can therefore reach DOM attributes without Angular's built-in sanitizer and execute arbitrary JavaScript in the user's browser context. Applications unable to upgrade can use DomSanitizer.sanitize with SecurityContext.URL before assignment or restrict inputs to validated HTTP and HTTPS URL schemes. This issue is fixed in versions 20.3.28, 21.2.20, and 22.1.0.
Quoted source text, attributed separately from HOL analysis.