Next.js Denial of Service (DoS) condition

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-39693: 0.49% estimated exploitation activity in the next 30 days; percentile 42.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A Denial of Service (DoS) condition was identified in Next.js. Exploitation of the bug can trigger a crash, affecting the availability of the server. This vulnerability can affect all Next.js deployments on the affected versions. Patches This vulnerability was resolved in Next.js 13.5 and later. We recommend that users upgrade to a safe version. Workarounds There are no official workarounds for this vulnerability. Credit Thai Vu of flyseccorp.com Aonan Guan (@0dd), Senior Cloud Security Engineer

Published by the source

10 Jul 2024, 16:03 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fq54-2j52-jc42

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-fq54-2j52-jc42

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-39693

Advisory: Next.js Denial of Service (DoS) condition
IDs: CVE-2024-39693, GHSA-fq54-2j52-jc42
Record: https://patchnext.com/advisories/cve-2024-39693 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: next 13.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm next: affected >= 13.3.1, < 13.5.0; fixed in 13.5.0

## Suggested inspection (read-only)
- `npm ls next --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on next.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fq54-2j52-jc42 (OSV record GHSA-fq54-2j52-jc42 lists affected ranges: npm next >=13.3.1 <13.5.0 (fixed))
- Verified: https://github.com/advisories/GHSA-fq54-2j52-jc42 (GitHub-reviewed advisory GHSA-fq54-2j52-jc42 lists affected ranges: npm next >=13.3.1 <13.5.0)

Commands are suggestions: review each one before running it.