CVE-2026-50171: @angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)
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.
Published Jun 15, 2026 · Updated Jul 15, 2026
Affected packages
@angular/common
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.0-rc.2
- Fixed in
- 22.0.0-rc.2
- Check
npm ls @angular/common
@angular/common
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0, < 20.3.22
- Fixed in
- 20.3.22
- Check
npm ls @angular/common
@angular/common
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.23
- Fixed in
- 19.2.23
- Check
npm ls @angular/common
@angular/common
- Ecosystem
- npm
- Affected
- <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/common
@angular/common
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.15
- Fixed in
- 21.2.15
- Check
npm ls @angular/common
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Impact
Successful exploitation of this vulnerability allows an attacker to trigger resource exhaustion, leading to a Denial of Service (DoS):
- Server-Side Rendering (SSR): In applications using SSR (e.g.,
@angular/ssr), an attacker can crash the Node.js server process due to aJavaScript heap out of memoryerror. This affects the availability of the application for all users. - Client-Side Rendering (CSR): In standard client-side applications, the unbounded loop will block the main thread, freezing the user's browser tab and making it unresponsive.
Attack Preconditions
For this vulnerability to be exploitable, the following conditions must be met:
- Vulnerable Component Usage: The application must use Angular's number formatting utilities, such as the
formatNumberfunction directly, or via template pipes (DecimalPipe,PercentPipe,CurrencyPipe). - Attacker-Controlled Parameter: The
digitsInfoparameter passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preference settings, or API responses that accept user-defined formatting options). IfdigitsInfois trusted or limited to a known, defined range for its value, the vulnerability is not exploitable by external attackers.
Patches
- 22.0.0-rc.2
- 21.2.15
- 20.3.22
- 19.2.23
Credits
This vulnerability was discovered and reported by CodeMender from Google DeepMind.
Credited to alan-agius4, JeanMeche, AndrewKushnir, josephperrott.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-111753
@angular/common: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)
medium5.9No fixOct 20, 2026CVE-2026-88059
Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`
medium4.0No fixSep 10, 2026CVE-2026-68945
Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
high8.8No fixAug 3, 2026CVE-2026-50170
@angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
high7.5No fixJun 15, 2026CVE-2026-54266
@angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
high6.1No fixJun 15, 2026CVE-2026-54268
@angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)
high7.5No fixJun 15, 2026
