CVE-2026-88058

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% 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
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 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.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
8.6
EG Score
8.6(medium)
EG Risk
55(Track*)
EG Risk 55/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
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
42%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 11, 2026

Advisory Details (9)

Auto-updated Sep 10, 2026
🔬 Proof of concept available. 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
generic

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 Patch Available🟡 PoC Available

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 21× 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-18 23:04 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 22:10 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 21:18 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 08:51 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 07:36 UTCEG score recompute
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 18:18 UTCEG score recompute
  12. 2026-09-13 16:48 UTCEPSS rescore
  13. 2026-09-12 17:24 UTCEG score recompute
  14. 2026-09-12 15:02 UTCEPSS rescore
  15. 2026-09-11 16:31 UTCEG score recompute
  16. 2026-09-11 15:19 UTCEG score recompute
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-10 19:18 UTCEG score recompute
  20. 2026-09-10 19:00 UTCEG score recompute
  21. 2026-09-10 18:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88058?
CVE-2026-88058 is a high 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.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 CVE-2026-88058 disclosed?
CVE-2026-88058 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-88058 actively exploited?
CVE-2026-88058 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 58.3% of all scored CVEs.
What is the CVSS score of CVE-2026-88058?
CVE-2026-88058 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-88058?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88058, 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

Explore the affected products and dependency analysis for 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.