CVE-2026-50171
DoS in Angular @angular/common digitsInfo parsing.
Is CVE-2026-50171 being exploited?
Not confirmed. CVE-2026-50171 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-50171?
CVE-2026-50171 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-50171?
Yes. A fix has been recorded for CVE-2026-50171. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50171 affect?
CVE-2026-50171 affects Angular framework ( @angular/common ) older versions: <22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50171?
Upgrade to fixed versions (≥22.0.0-rc.2 or 21.2.15/20.3.22/19.2.23).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
DoS: crafted digitsInfo causes unbounded loop in formatNumber, exhausting CPU/memory.
Patch when possible
- affected>= 22.0.0-next.0 and < 22.0.0-rc.2
- affected>= 21.0.0-next.0 and < 21.2.15
- affected>= 20.0.0-next.0 and < 20.3.22
- affected>= 19.0.0-next.0 and < 19.2.23
- affected<= 18.2.14
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.