Skip to content
Fencer Intel
medium 6.1

CVE-2026-88057 json

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

published 2mo ago modified last mo. also EUVD-2026-75678 , GHSA-hh8m-fm6v-7cvg

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @angular/core 20.3.28, 21.2.20, 22.1.0
  • npm @angular/compiler 20.3.28, 21.2.20, 22.1.0
  • angular angular 20.3.28, 21.2.20, 22.1.0
  • angular angular/core 20.3.28, 21.2.20, 22.1.0

Is CVE-2026-88057 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-88057 updated cvss 5.4

@angular/core: @angular/compiler: Angular: Arbitrary code execution via sanitization bypass in host bindings

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/volsync-rhel9, rhacm2/volsync-operator-bundle
    affected: no fix planned “Out of support scope”
  • Red Hat build of Apicurio Registry 3 apicurio/apicurio-registry-ui-rhel8, apicurio/apicurio-registry-gitops-sync-rhel9
    affected: no fix available, no fix planned “Out of support scope”
  • Red Hat Ceph Storage 4 ceph, librbd1, librgw2, rbd-nbd, ceph-mds, ceph-mgr, +27 more Red Hat Enterprise Linux 7 firefox, firefox 140.14.0-1.el10_2 Red Hat Enterprise Linux 8 mozjs60, intel-cmt-cat 25.04-1.el10 Red Hat Enterprise Linux 9 firefox, librbd1, dotnet6.0, dotnet7.0, librados2, dotnet-host, +25 more Red Hat Enterprise Linux 10 ceph, gjs 1.80.2-11.el10, firefox 140.14.0-1.el10_2, intel-cmt-cat 25.04-1.el10, thunderbird 140.14.0-1.el10_2
    affected: no fix available “Fix deferred”
  • Red Hat Fuse 7 core 11.2.14, compiler 11.2.14
    affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/angular/angular/security/advisories/GHSA-hh8m-fm6v-7cvg referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 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
CNA 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm @angular/core
>=22.0.0, <22.1.0
>=21.0.0, <21.2.20
>=20.0.0, <20.3.28
<=19.2.25
22.1.0
21.2.20
20.3.28
npm @angular/compiler
>=22.0.0, <22.1.0
>=21.0.0, <21.2.20
>=20.0.0, <20.3.28
<=19.2.25
22.1.0
21.2.20
20.3.28

Affected products

  • angular angular

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of angular/angular published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.