Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler

CVE-2026-88057GHSA-hh8m-fm6v-7cvg

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @angular/compiler

    Affected
    >= 22.0.0, < 22.1.0>= 21.0.0, < 21.2.20>= 20.0.0, < 20.3.28<= 19.2.25
    Fixed in
    22.1.0, 20.3.28, 21.2.20

  • npm @angular/core

    Affected
    >= 22.0.0, < 22.1.0>= 21.0.0, < 21.2.20>= 20.0.0, < 20.3.28<= 19.2.25
    Fixed in
    22.1.0, 20.3.28, 21.2.20

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · 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 · score source
EPSS
  • CVE-2026-88057: 0.37% estimated exploitation activity in the next 30 days; percentile 31.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Angular automatically sanitizes untrusted values bound to security-sensitive DOM sinks (such as href, src, action, xlink:href, and data) to protect against Cross-Site Scripting (XSS). Prior to the fix, the Angular compiler determined the SecurityContext for directive host bindings (host: {'[attr.href]': 'value'} or @HostBinding('attr.href')) based solely on the declaring directive or component selector at compile time, rather than the concrete host element that the directive was applied to. When a directive with a security-sensitive host binding was applied to a different concrete host element—such as through: - hostDirectives composition, - Class inheritance of host bindings, - Dynamic component instantiation (createComponent with custom hostElement or dynamic directives), - Elements with SVG/MathML namespaces (e.g. <svg:a, <math), or - Elements using tag-neutral selectors (e.g. :not(...)), the compiler either failed to associate a sanitizer with the host binding or attached an…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-hh8m-fm6v-7cvg

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-hh8m-fm6v-7cvg

  4. Revision 1 · created ·

    Published from ghsa record GHSA-hh8m-fm6v-7cvg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88057

Advisory: Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
IDs: CVE-2026-88057, GHSA-hh8m-fm6v-7cvg
Record: https://patchnext.com/advisories/cve-2026-88057 (revision 4, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @angular/compiler 22.1.0, 21.2.20, 20.3.28; @angular/core 22.1.0, 21.2.20, 20.3.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @angular/compiler: affected >= 22.0.0, < 22.1.0; >= 21.0.0, < 21.2.20; >= 20.0.0, < 20.3.28; <= 19.2.25; fixed in 22.1.0, 20.3.28, 21.2.20
- npm @angular/core: affected >= 22.0.0, < 22.1.0; >= 21.0.0, < 21.2.20; >= 20.0.0, < 20.3.28; <= 19.2.25; fixed in 22.1.0, 20.3.28, 21.2.20

## Suggested inspection (read-only)
- `npm ls @angular/compiler --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @angular/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @angular/compiler, @angular/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hh8m-fm6v-7cvg (GitHub-reviewed advisory GHSA-hh8m-fm6v-7cvg lists affected ranges: npm @angular/core >=22.0.0 =21.0.0 =20.0.0 =0 =22.0.0 =21.0.0 =20.0.0 =0 <=19.2.25)
- Verified: https://osv.dev/vulnerability/GHSA-hh8m-fm6v-7cvg (OSV record GHSA-hh8m-fm6v-7cvg lists affected ranges: npm @angular/core >=22.0.0 =21.0.0 =20.0.0 =0 =22.0.0 =21.0.0 =20.0.0 =0 <=19.2.25)

Commands are suggestions: review each one before running it.

Loading voting…