Packages / next / Security

HighVulnerabilityGHSA-25mp-g6fv-mqxxCVE-2021-43803Published 7 Dec 2021

Unexpected server crash in Next.js.

Affected releases · next

  • 12.x12.0.0 – 12.0.4Fixed in 12.0.5
  • 11.x11.0.0 – 11.1.2Fixed in 11.1.3
  • 10.x and older0.9.9 – 10.2.3No fix, no longer updated

On 12.x, the newest line:

npm install next@12.0.5
16.x

  1. Not affected

    16.0.0 – 16.4.2

    45 releases, latest

12.x

  1. Affected

    12.0.0 – 12.0.4

    5 releases

  2. Fixed

    12.0.5 – 12.3.7

    28 releases

11.x

  1. Affected

    11.0.0 – 11.1.2

    5 releases

  2. Fixed

    11.1.3 – 11.1.4

    2 releases

10.x

  1. Affected

    10.0.0 – 10.2.3

    18 releases

9.x

  1. Affected

    9.0.0 – 9.5.5

    38 releases

8.x

  1. Affected

    8.0.0 – 8.1.0

    6 releases

7.x

  1. Affected

    7.0.0 – 7.0.3

    4 releases

6.x

  1. Affected

    6.0.0 – 6.1.2

    7 releases

5.x

  1. Affected

    5.0.0 – 5.1.0

    2 releases

4.x

  1. Affected

    4.0.0 – 4.2.3

    15 releases

3.x

  1. Affected

    3.0.1 – 3.2.3

    11 releases

2.x

  1. Affected

    2.0.0 – 2.4.9

    17 releases

1.x

  1. Affected

    1.0.0 – 1.2.3

    10 releases

0.x

  1. Not affected

    0.1.0 – 0.4.1

    23 releases

  2. Affected

    0.9.9 – 0.9.11

    3 releases

423 stable releases of next, oldest to newest, one row per major.

Is your project affected?

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

What happens

Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package next hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.