CVE-2026-101896
Angular SSR URL parsing allows heap-exhaustion DoS via numeric matrix params.
Is CVE-2026-101896 being exploited?
Not confirmed. CVE-2026-101896 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-101896?
CVE-2026-101896 is rated High with a CVSS score of 8.2. 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-101896?
Yes. A fix has been recorded for CVE-2026-101896. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-101896 affect?
CVE-2026-101896 affects Angular < 20.3.32 (20.x), Angular < 21.2.24 (21.x), Angular < 22.2.0 (22.x), Applications using Angular server-side rendering (Angular Universal) parsing raw URLs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-101896?
Upgrade to 20.3.32, 21.2.24, or 22.2.0+; validate/sanitize URLs and block semicolon path segments at proxy.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can exhaust Node.js old-space heap in Angular SSR by sending crafted URLs with repeated numeric matrix params, causing SSR worker termination and service outage.
Patch when possible
- affected<= 19.2.25
- affected>= 20.0.0 and < 20.3.32
- affected>= 21.0.0 and < 21.2.24
- affected>= 22.0.0 and < 22.2.0
- affected<= 19.2.25
- affected>= 20.0.0 and < 20.3.32
- affected>= 21.0.0 and < 21.2.24
- affected>= 22.0.0 and < 22.2.0
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.