Skip to content
Web

CVE-2026-101895

8.7
High
EPSS 0.72%Patch availableOct 17, 2026

Angular SSR parser infinite-loop DoS via crafted incomplete DOCTYPE

common questions

Is CVE-2026-101895 being exploited?

Not confirmed. CVE-2026-101895 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.

How severe is CVE-2026-101895?

CVE-2026-101895 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-101895?

Yes. A fix has been recorded for CVE-2026-101895. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-101895 affect?

CVE-2026-101895 affects @angular/platform-server (< 20.3.31, < 21.2.23, < 22.1.6), domino lib/HTMLParser.js, Node.js SSR apps using Angular Universal. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-101895?

Upgrade to 20.3.31 / 21.2.23 / 22.1.6+ and sanitize/validate untrusted HTML

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
@angular/platform-server (< 20.3.31, < 21.2.23, < 22.1.6)domino lib/HTMLParser.jsNode.js SSR apps using Angular Universal
impact

Remote attacker can send crafted HTML to Node.js SSR (Angular Universal) to trigger an infinite loop, consuming CPU, starving event loop and causing service DoS.

action required

Patch when possible

affected versions
angular angular
  • affected<= 19.2.25
  • affected>= 20.0.0 and < 20.3.31
  • affected>= 21.0.0 and < 21.2.23
  • affected>= 22.0.0 and < 22.1.6
@angular/ platform-server
  • affected<= 19.2.25
  • affected>= 20.0.0 and < 20.3.31
  • affected>= 21.0.0 and < 21.2.23
  • affected>= 22.0.0 and < 22.1.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free