CVE-2026-88057

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-75678 (ENISA EUVD) · GHSA-hh8m-fm6v-7cvg (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 10, 2026

Last Modified

September 29, 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 pull request

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
Web page

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

https://github.com/angular/angular/issues/69550
GitHub advisoryMentions a patch (unverified)

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.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/compiler @ 22.1.0 (fixes >= 22.0.0, < 22.1.0)—ghsa
npm@angular/compiler @ 20.3.28 (fixes >= 20.0.0, < 20.3.28)—ghsa
npm@angular/compiler @ 21.2.20 (fixes >= 21.0.0, < 21.2.20)—ghsa
npm@angular/compiler—ghsa
npm@angular/core—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@angular/compiler—
  • 22.0.0 up to 22.1.0: fixed in 22.1.0
  • 21.0.0 up to 21.2.20: fixed in 21.2.20
  • 20.0.0 up to 20.3.28: fixed in 20.3.28
  • every version through 19.2.25: no fix on record
—
@angular/core—
  • 22.0.0 up to 22.1.0: fixed in 22.1.0
  • 21.0.0 up to 21.2.20: fixed in 21.2.20
  • 20.0.0 up to 20.3.28: fixed in 20.3.28
  • every version through 19.2.25: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 96 is merged into the row it repeats.

  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-hh8m-fm6v-7cvg · GitHub severity MODERATE
  5. 2026-11-01 07:37 UTCEG score recompute
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-29 22:55 UTCOSV refresh
  9. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-25 13:53 UTCEG score recompute
  15. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-22 12:33 UTCEG score recompute
  19. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-10-18 03:03 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 70 more
  1. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-12 14:49 UTCEG score recompute
  6. 2026-10-11 19:15 UTCEG score recompute
  7. 2026-10-11 16:32 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-11 13:49 UTCEG score recompute
  10. 2026-10-10 20:09 UTCEG score recompute
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-09 21:57 UTCEG score recompute
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-08 23:59 UTCEG score recompute
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-08 02:06 UTCEG score recompute
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-10-07 04:12 UTCEG score recompute
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-06 06:18 UTCEG score recompute
  21. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-10-05 07:56 UTCEG score recompute
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-04 10:02 UTCEG score recompute
  25. 2026-10-03 12:08 UTCEG score recompute
  26. 2026-10-02 13:20 UTCEG score recompute
  27. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  28. 2026-09-30 17:18 UTCEG score recompute
  29. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  30. 2026-09-29 19:13 UTCEG score recompute▲ 0.80
  31. 2026-09-29 19:06 UTCNVD updateCVSS v3 → 6.1
  32. 2026-09-29 05:44 UTCEG score recompute
  33. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  34. 2026-09-28 07:50 UTCEG score recompute
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-09-27 09:57 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  38. 2026-09-26 12:04 UTCEG score recompute
  39. 2026-09-24 16:04 UTCEG score recompute
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  41. 2026-09-23 18:10 UTCEG score recompute
  42. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  43. 2026-09-22 20:17 UTCEG score recompute
  44. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-09-21 22:19 UTCEG score recompute
  46. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  47. 2026-09-21 00:24 UTCEG score recompute
  48. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-09-20 02:29 UTCEG score recompute
  50. 2026-09-19 04:34 UTCEG score recompute
  51. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-09-18 06:40 UTCEG score recompute
  53. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-09-17 08:47 UTCEG score recompute
  55. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-09-16 10:53 UTCEG score recompute
  57. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  58. 2026-09-15 12:59 UTCEG score recompute
  59. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-09-13 17:11 UTCEG score recompute
  61. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  62. 2026-09-12 19:17 UTCEG score recompute
  63. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  64. 2026-09-11 21:23 UTCEG score recompute
  65. 2026-09-11 20:47 UTCEG score recompute
  66. 2026-09-11 17:52 UTCEG score recompute
  67. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  68. 2026-09-10 19:18 UTCEG score recompute
  69. 2026-09-10 18:55 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  70. 2026-09-10 18:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88057?
CVE-2026-88057 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-88057 published?
The CVE record for CVE-2026-88057 was published on September 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-88057 actively exploited?
CVE-2026-88057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88057?
CVE-2026-88057 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-88057?
A fix for CVE-2026-88057 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88057 are linked in the Vendor Advisories panel on this page.

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.