CVE-2026-88058

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.3% (20th 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 weekElevated

Also known asEUVD-2026-75681 (ENISA EUVD) · GHSA-j3r3-mxqp-r2p4 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: No code on recordExposed 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.30, 21.2.22, and 22.1.4, Angular server-side rendering (SSR) in @angular/platform-server serializes ProcessingInstruction DOM nodes inside fallback raw-content elements without escaping matching ancestor closing tags. ProcessingInstruction data escaped greater-than characters but left less-than characters untouched and did not inspect fallback ancestors, so data such as a matching closing tag prematurely terminates noscript, iframe, noembed, or noframes containers. The vulnerable nodes cannot be authored through standard Angular templates; reachability requires application or library code using inject(DOCUMENT).createProcessingInstruction with attacker-controlled data or Renderer2 DOM insertion inside a fallback container. In HTML5 RAWTEXT parsing, the premature close causes subsequent sibling elements to be interpreted as live HTML and enables arbitrary JavaScript execution in a victim's browser. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.

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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
20th
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.3% 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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_commit, github_release.
GitHub release Patch Available

22.1.4

Patch available: angular/angular v22.1.4

https://github.com/angular/angular/releases/tag/v22.1.4
GitHub release Patch Available

21.2.22

Patch available: angular/angular v21.2.22

https://github.com/angular/angular/releases/tag/v21.2.22
GitHub release Patch Available

20.3.30

Patch available: angular/angular v20.3.30

https://github.com/angular/angular/releases/tag/v20.3.30
GitHub commit

commit 04f987dc08ff (angular/domino)

Fix landed in angular/domino commit 04f987dc08ff — awaiting tagged release

https://github.com/angular/domino/commit/04f987dc08ff3736b427f50941adf1722458528f
GitHub commit Patch Available

commit ba3bc47b20b3 (angular/angular)

Patch available: angular/angular v22.1.4 (contains commit ba3bc47b20b3)

https://github.com/angular/angular/commit/ba3bc47b20b3d12f5eb141ec9c651373ae4d15e8
GitHub commit Patch Available

commit 89b20568dfae (angular/angular)

Patch available: angular/angular v20.3.30 (contains commit 89b20568dfae)

https://github.com/angular/angular/commit/89b20568dfaee1ec8e0b3bcf1872acdddd2f4fef
GitHub commit Patch Available

commit 73d8bbd27cb4 (angular/angular)

Patch available: angular/angular v21.2.22 (contains commit 73d8bbd27cb4)

https://github.com/angular/angular/commit/73d8bbd27cb46495426d4132975a1355b47ad915
Web page

Incomplete fix for #70050 / #70055: `</noscript>` breakout still reachable through processing instructions · Issue #70146 · angular/angular · GitHub

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

SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-j3r3-mxqp-r2p4

Vendor Advisories for CVE-2026-88058(1)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/platform-server @ 22.1.4 (fixes >= 22.0.0, < 22.1.4)—ghsa
npm@angular/platform-server @ 21.2.22 (fixes >= 21.0.0, < 21.2.22)—ghsa
npm@angular/platform-server @ 20.3.30 (fixes >= 20.0.0, < 20.3.30)—ghsa
npm@angular/platform-server—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

(3 across 3 ecosystems)
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
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/platform-server—
  • 22.0.0 up to 22.1.4: fixed in 22.1.4
  • 21.0.0 up to 21.2.22: fixed in 21.2.22
  • 20.0.0 up to 20.3.30: fixed in 20.3.30
  • every version through 19.2.25: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 46× 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 92 is merged into the row it repeats.

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

Frequently asked(5)

What is CVE-2026-88058?
CVE-2026-88058 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.30, 21.2.22, and 22.1.4, Angular server-side rendering (SSR) in @angular/platform-server serializes ProcessingInstruction DOM nodes inside fallback…
When was the CVE record for CVE-2026-88058 published?
The CVE record for CVE-2026-88058 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-88058 actively exploited?
CVE-2026-88058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88058?
CVE-2026-88058 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-88058?
A fix for CVE-2026-88058 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88058 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-88058

Explore →

Is Your Infrastructure Affected by CVE-2026-88058?

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