CVE-2026-101895

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-101126 (ENISA EUVD) · GHSA-f67j-2jqw-jpq7 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
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.9%CVSS: 8.7Exploit: 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.31, 21.2.23, and 22.1.6, the @angular/platform-server DOM emulation parser can enter an infinite synchronous loop when Angular server-side rendering processes attacker-controlled HTML containing an incomplete DOCTYPE that ends with whitespace at end of input. In Domino lib/HTMLParser.js, after_doctype_name_state emits doctype and EOF tokens without advancing nextchar or leaving the fixed-lookahead state, so the scanner repeatedly handles the same EOF marker. A remote unauthenticated attacker can use this condition through server-side HTML parsing paths such as innerHTML binding to consume a Node.js SSR worker at full CPU, starve the event loop, and stop concurrent and subsequent requests. This issue is fixed in versions 20.3.31, 21.2.23, and 22.1.6.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 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.
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 public PoC (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.9%
EPSS %ILE
58th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.9% 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 public PoC (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 28, 2026

Last Modified

October 16, 2026

Advisory Details (7)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

22.1.6

Patch available: angular/angular v22.1.6

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

21.2.23

Patch available: angular/angular v21.2.23

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

20.3.31

Patch available: angular/angular v20.3.31

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

commit 4d97473116d0 (angular/domino)

Fix landed in angular/domino commit 4d97473116d0 — awaiting tagged release

https://github.com/angular/domino/commit/4d97473116d000e3fd4d6f75ec98cbd67576fa6f
GitHub commit Patch Available

commit fc2e8fbc0bda (angular/angular)

Patch available: angular/angular v21.2.23 (contains commit fc2e8fbc0bda)

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

commit 3db26e254496 (angular/angular)

Patch available: angular/angular v20.3.31 (contains commit 3db26e254496)

https://github.com/angular/angular/commit/3db26e2544964d07a520836ad01f02f36ec88e25
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Denial of Service (DoS) via Infinite Loop on Malformed DOCTYPE in Angular SSR · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-f67j-2jqw-jpq7

Vendor Advisories for CVE-2026-101895(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.6 (fixes >= 22.0.0, < 22.1.6)—ghsa
npm@angular/platform-server @ 21.2.23 (fixes >= 21.0.0, < 21.2.23)—ghsa
npm@angular/platform-server @ 20.3.31 (fixes >= 20.0.0, < 20.3.31)—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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/platform-server—
  • 22.0.0 up to 22.1.6: fixed in 22.1.6
  • 21.0.0 up to 21.2.23: fixed in 21.2.23
  • 20.0.0 up to 20.3.31: fixed in 20.3.31
  • 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 10× in last 7d / 34× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-f67j-2jqw-jpq7 · GitHub severity HIGH
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-27 20:35 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-10-25 14:57 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-20 19:16 UTCEG score recompute
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-18 05:11 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-16 16:10 UTCEG score recompute
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 10 more
  1. 2026-10-14 18:26 UTCEG score recompute
  2. 2026-10-14 17:51 UTCEG score recompute
  3. 2026-10-14 15:31 UTCEG score recompute
  4. 2026-10-14 15:06 UTCEG score recomputeFirst assessed: 8.7 HIGH
  5. 2026-10-14 15:04 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7
  6. 2026-10-12 16:41 UTCEG score recompute
  7. 2026-10-11 20:16 UTCEG score recompute
  8. 2026-10-11 18:28 UTCEG score recompute
  9. 2026-10-11 15:02 UTCEG score recompute
  10. 2026-09-28 22:10 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-101895?
CVE-2026-101895 is a high-severity vulnerability; its CVE record was published on September 28, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.31, 21.2.23, and 22.1.6, the @angular/platform-server DOM emulation parser can enter an infinite synchronous loop when Angular server-side rendering…
When was the CVE record for CVE-2026-101895 published?
The CVE record for CVE-2026-101895 was published on September 28, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-101895 actively exploited?
CVE-2026-101895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101895?
CVE-2026-101895 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101895?
A fix for CVE-2026-101895 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101895 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-101895

Explore →

Is Your Infrastructure Affected by CVE-2026-101895?

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

Book a Demo →Browse All CVEs