dbcve.org
Next.jsApplication · Vercel

CVE-2024-39693

HIGH · 7.5 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 13.5.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Next.js is a React framework. 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. his vulnerability was resolved in Next.js 13.5 and later.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A Denial of Service (DoS) vulnerability in Next.js allows attackers to crash the server, impacting availability. The vulnerability was addressed in Next.js version 13.5 and later.

MitigationUpgrade to Next.js 13.5 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Next.jsApplication
Affected:>= 13.3.1, < 13.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Next.js version
    Run 'npm list next' or 'npm list react' to see the Next.js version in your project dependencies
    Affected if The version listed is 13.3.1, 13.3.2, 13.4.x, or any 13.5.0-beta/rc version below 13.5.0 final release
  2. Verify version in package.json
    Open your project's package.json file and check the 'dependencies' or 'devDependencies' section for the 'next' package version
    Affected if The version specified is >= 13.3.1 and < 13.5.0 (such as 13.3.1, 13.4.0, 13.4.12, etc.)
  3. Check node_modules version directly
    Inspect the node_modules/next/package.json file to confirm the installed Next.js version
    Affected if The version in node_modules/next/package.json is 13.3.1 through 13.4.x or any prerelease version below 13.5.0

You are affected if your deployed Next.js version is 13.3.1 or any 13.4.x version, or if you are using a 13.5.0 prerelease version prior to the official 13.5.0 release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.5.0 or later
Fixed in 13.5.0
Interim mitigation

Upgrade to Next.js 13.5 or later to remediate this vulnerability.

Recommended fix High confidence

Next.js 13.5.0 or later

  1. Upgrade Next.js to version 13.5.0 or later by running: npm install [email protected] (or yarn add [email protected], or pnpm add [email protected])
  2. After upgrading, verify the application functions correctly and test for any regressions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Next.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39693 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39693 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data