CVE-2026-50171: Angular: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

Published Jun 15, 2026
·
Updated

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 a JavaScript heap out of memory error. 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:

1. Vulnerable Component Usage: The application must use Angular's number formatting utilities, such as the formatNumber function directly, or via template pipes (DecimalPipe, PercentPipe, CurrencyPipe). 2. Attacker-Controlled Parameter: The digitsInfo parameter 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). If digitsInfo is 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.

Other sources

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.

MITRE

Affected Software

24 affected componentsFixes available
npm/@angular/common>=21.0.0-next.0<21.2.15
21.2.15
npm/@angular/common<=18.2.14
npm/@angular/common>=19.0.0-next.0<19.2.23
19.2.23
npm/@angular/common>=20.0.0-next.0<20.3.22
20.3.22
npm/@angular/common>=22.0.0-next.0<22.0.0-rc.2
22.0.0-rc.2
angular Angular Node.js<=18.2.14
angular Angular Node.js>=19.0.0<19.2.23
angular Angular Node.js>=20.0.0<20.3.22
angular Angular Node.js>=21.0.0<21.2.15
angular Angular Node.js=22.0.0-next0
angular Angular Node.js=22.0.0-next1
angular Angular Node.js=22.0.0-next10
angular Angular Node.js=22.0.0-next11
angular Angular Node.js=22.0.0-next12
angular Angular Node.js=22.0.0-next2
angular Angular Node.js=22.0.0-next3
angular Angular Node.js=22.0.0-next4
angular Angular Node.js=22.0.0-next5
angular Angular Node.js=22.0.0-next6
angular Angular Node.js=22.0.0-next7
angular Angular Node.js=22.0.0-next8
angular Angular Node.js=22.0.0-next9
angular Angular Node.js=22.0.0-rc0
angular Angular Node.js=22.0.0-rc1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@angular/common to a version that resolves this vulnerability.

    Fixed in 21.2.15
  2. Upgrade

    Upgrade npm/@angular/common to a version that resolves this vulnerability.

    Fixed in 19.2.23
  3. Upgrade

    Upgrade npm/@angular/common to a version that resolves this vulnerability.

    Fixed in 20.3.22
  4. Upgrade

    Upgrade npm/@angular/common to a version that resolves this vulnerability.

    Fixed in 22.0.0-rc.2
  5. Upgrade

    Upgrade @angular/common to a version that resolves this vulnerability.

    Fixed in 22.0.0-rc.2
  6. Upgrade

    Upgrade @angular/common to a version that resolves this vulnerability.

    Fixed in 21.2.15
  7. Upgrade

    Upgrade @angular/common to a version that resolves this vulnerability.

    Fixed in 20.3.22
  8. Upgrade

    Upgrade @angular/common to a version that resolves this vulnerability.

    Fixed in 19.2.23
  9. Configuration

    Ensure the digitsInfo parameter is trusted or constrained to a known safe range. Reject or clamp excessively large fraction digit values in the digitsInfo string (e.g., prevent inputs like `1.200000000-200000000`) before passing it to Angular's number formatting (formatNumber / DecimalPipe / PercentPipe / CurrencyPipe).

    Angular number formatting utilities (@angular/common: formatNumber / DecimalPipe / PercentPipe / CurrencyPipe) digitsInfo upper bound validation = Enforce a trusted, limited range for digitsInfo (minimum/maximum fraction digits) before calling formatNumber or using DecimalPipe/PercentPipe/CurrencyPipe

Event History

Jun 15, 2026
Advisory Published
via GitHub·04:52 PM
Data Sourced
via GitHub·04:52 PM
DescriptionWeaknessAffected Software
Jun 22, 2026
CVE Published
via MITRE·03:49 PM
Data Sourced
via MITRE·03:49 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-50171?

CVE-2026-50171 has a risk rating of 30, indicating a critical Denial of Service vulnerability.

2

How do I fix CVE-2026-50171?

To fix CVE-2026-50171, update the `@angular/common` package to the latest version that addresses this vulnerability.

3

What components are affected by CVE-2026-50171?

CVE-2026-50171 affects the `formatNumber` function, and by extension, the `DecimalPipe`, `PercentPipe`, and `CurrencyPipe` within the `@angular/common` package.

4

What kind of attack is possible with CVE-2026-50171?

CVE-2026-50171 allows an attacker to exploit the vulnerability to cause a Denial of Service (DoS), potentially affecting application availability.

5

When was CVE-2026-50171 published?

CVE-2026-50171 was published on June 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203