CVE-2026-50171

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% 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, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 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 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a Denial of Service (DoS) vulnerability exists in the @angular/common package of Angular. The formatNumber function, which is also utilized by DecimalPipe, PercentPipe, and CurrencyPipe, does not properly validate the upper bounds of the digitsInfo parameter. Specifically, the minimum and maximum fraction digits parsed from the digitsInfo string (e.g., 1.2-4) are converted to integers and used without limits. When parsing a maliciously crafted digitsInfo string with excessively large fraction digit values (e.g., 1.200000000-200000000), the internal roundNumber function attempts to pad the digits array to match the requested fraction size. This results in an unbounded loop that repeatedly pushes elements into an array. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
5.6%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github.
github Patch Available

Denial of Service (DoS) via OOM in Number Formatting (digitsInfo) · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-p3vc-36g9-x9gr

Vendor Advisories for CVE-2026-50171(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@angular/common21.2.15

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 37× 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-07-07 00:23 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 10:40 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 10:04 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 04:09 UTCEG score recompute
  9. 2026-07-02 03:05 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 02:32 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 01:59 UTCEG score recompute
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 01:26 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 00:53 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-27 00:20 UTCEG score recompute 2.10
  23. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  24. 2026-06-26 11:58 UTCEG score recompute
  25. 2026-06-25 21:42 UTCEG score recompute
Show 12 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-25 09:23 UTCEG score recompute
  3. 2026-06-24 21:04 UTCEG score recompute
  4. 2026-06-24 14:05 UTCEPSS rescore
  5. 2026-06-24 08:45 UTCEG score recompute
  6. 2026-06-23 21:33 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 20:27 UTCEG score recompute
  9. 2026-06-23 08:06 UTCEG score recompute
  10. 2026-06-22 19:43 UTCEG score recompute 8.20
  11. 2026-06-22 19:40 UTCNVD updateCVSS v3 → 8.2 · CVSS v4 → 8.2
  12. 2026-06-15 17:16 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50171?
CVE-2026-50171 is a medium vulnerability published on June 15, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, a Denial of Service (DoS) vulnerability exists in the @angular/common package of Angular. The formatNumber…
When was CVE-2026-50171 disclosed?
CVE-2026-50171 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50171 actively exploited?
CVE-2026-50171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50171?
CVE-2026-50171 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-50171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50171, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50171

Explore →

Is Your Infrastructure Affected by CVE-2026-50171?

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