Packages / @angular/common / Security

HighVulnerabilityGHSA-p3vc-36g9-x9grCVE-2026-50171Published 15 Jun 2026

@angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)

Affected releases · @angular/common

  • 21.x21.0.0 – 21.2.14Fixed in 21.2.15
  • 20.x20.0.0 – 20.3.21Fixed in 20.3.22
  • 19.x19.0.0 – 19.2.22Fixed in 19.2.23
  • 18.x and older2.0.0 – 18.2.14No fix, no longer updated

On 21.x, the newest line:

npm install @angular/common@21.2.15
22.x
  1. Not affected

    22.0.0 – 22.2.3

    22 releases, latest

21.x
  1. Affected

    21.0.0 – 21.2.14

    32 releases

  2. Fixed

    21.2.15 – 21.2.25

    11 releases

20.x
  1. Affected

    20.0.0 – 20.3.21

    43 releases

  2. Fixed

    20.3.22 – 20.3.34

    13 releases

19.x
  1. Affected

    19.0.0 – 19.2.22

    40 releases

  2. Fixed

    19.2.23 – 19.2.25

    3 releases

18.x
  1. Affected

    18.0.0 – 18.2.14

    29 releases

17.x
  1. Affected

    17.0.0 – 17.3.12

    32 releases

16.x
  1. Affected

    16.0.0 – 16.2.12

    30 releases

15.x
  1. Affected

    15.0.0 – 15.2.10

    22 releases

14.x
  1. Affected

    14.0.0 – 14.3.0

    26 releases

13.x
  1. Affected

    13.0.0 – 13.4.0

    30 releases

12.x
  1. Affected

    12.0.0 – 12.2.17

    30 releases

11.x
  1. Affected

    11.0.0 – 11.2.14

    28 releases

10.x
  1. Affected

    10.0.0 – 10.2.5

    28 releases

9.x
  1. Affected

    9.0.0 – 9.1.13

    22 releases

8.x
  1. Affected

    8.0.0 – 8.2.14

    23 releases

7.x
  1. Affected

    7.0.0 – 7.2.16

    27 releases

6.x
  1. Affected

    6.0.0 – 6.1.10

    20 releases

5.x
  1. Affected

    5.0.0 – 5.2.11

    22 releases

4.x
  1. Affected

    4.0.0 – 4.4.7

    30 releases

2.x
  1. Affected

    2.0.0 – 2.4.10

    24 releases

587 stable releases of @angular/common, oldest to newest, one row per major.

Is your project affected?

Paste your package.json, or type the range you declare for @angular/common. It is read in your browser and sent nowhere.

What happens

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.