CVE-2026-88057

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 11, 2026

Advisory Details (9)

Auto-updated Sep 10, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

22.1.0

Patch available: angular/angular v22.1.0

https://github.com/angular/angular/releases/tag/v22.1.0
github_release Patch Available

21.2.20

Patch available: angular/angular v21.2.20

https://github.com/angular/angular/releases/tag/v21.2.20
github_release Patch Available

20.3.28

Patch available: angular/angular v20.3.28

https://github.com/angular/angular/releases/tag/v20.3.28
github_commit

commit 6caa298dee58 (angular/angular)

Fix landed in angular/angular commit 6caa298dee58 — awaiting tagged release

https://github.com/angular/angular/commit/6caa298dee58319b2d674dc91364e26ffe3ecb2b
github_commit Patch Available

commit 6afe6fa781c2 (angular/angular)

Patch available: angular/angular v21.2.20 (contains commit 6afe6fa781c2)

https://github.com/angular/angular/commit/6afe6fa781c2f0931f0aedd729b9884a8fe212ee
github_commit Patch Available

commit 2f96c8020f85 (angular/angular)

Patch available: angular/angular v20.3.28 (contains commit 2f96c8020f85)

https://github.com/angular/angular/commit/2f96c8020f85ccb715a76de4b79a0c680c2c7264
github_pr

fix(core): sanitize host bindings on concrete hosts

Upstream fix in progress (PR #69558 · angular/angular, state=closed)

https://github.com/angular/angular/pull/69558
generic

ResourceURL sanitizer bypass through host-binding selector mismatch · Issue #69550 · angular/angular · GitHub

https://github.com/angular/angular/issues/69550
github Patch Available

Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-hh8m-fm6v-7cvg

Vendor Advisories for CVE-2026-88057(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
@angular/compiler—22.1.0—
@angular/core—22.1.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 04:34 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 06:40 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 08:47 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 10:53 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 12:59 UTCEG score recompute
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 17:11 UTCEG score recompute
  12. 2026-09-13 16:48 UTCEPSS rescore
  13. 2026-09-12 19:17 UTCEG score recompute
  14. 2026-09-12 15:02 UTCEPSS rescore
  15. 2026-09-11 21:23 UTCEG score recompute
  16. 2026-09-11 20:47 UTCEG score recompute
  17. 2026-09-11 17:52 UTCEG score recompute
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-10 19:18 UTCEG score recompute
  21. 2026-09-10 18:55 UTCEG score recompute
  22. 2026-09-10 18:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88057?
CVE-2026-88057 is a medium vulnerability published on September 10, 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…
When was CVE-2026-88057 disclosed?
CVE-2026-88057 was first published in the National Vulnerability Database on September 10, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88057 actively exploited?
CVE-2026-88057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.2% of all scored CVEs.
What is the CVSS score of CVE-2026-88057?
CVE-2026-88057 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-88057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88057, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88057

Explore →

Is Your Infrastructure Affected by CVE-2026-88057?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs