Skip to main content
No exploitation reportedFix available

CVE-2024-34350

No exploitation reported by the sources we read.

  • Published2024-05-14
  • Fixed in13.5.1
  • WeaknessCWE-444

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Next.js is a React framework that can provide building blocks to create web applications. Prior to 13.5.1, an inconsistent interpretation of a crafted HTTP request meant that requests are treated as both a single request, and two separate requests by Next.js, leading to desynchronized responses. This led to a response queue poisoning vulnerability in the affected Next.js versions. For a request to be exploitable, the affected route also had to be making use of the [rewrites](https://nextjs.org/docs/app/api-reference/next-config-js/rewrites) feature in Next.js. The vulnerability is resolved in Next.js `13.5.1` and newer.

Timeline

dates in UTC
  1. 2024-05-1415:38CVE publishedNVD

Versions per branch

NVD · OSV
Next.js
BranchAffectedFixed in
13.x≥ 13.4.0, < 13.5.113.5.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • vercel next.js
    Affected
    • = >= 13.4.0, < 13.5.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-05-09

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.6
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.2
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.3
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.4
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.5
  • @rootio/nextRoot:npmall versions · fixed in 13.4.19-root.io.7
  • nextRoot:npmall versions · fixed in 13.4.19-aikido.6
  • nextRoot:npmall versions · fixed in 13.4.19-aikido.2

4 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Next.js to 13.5.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2024-05-09
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-444known since 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2024-05-09

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2024-05-14
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-77r5-gw3j-2mpf

Frequently asked questions

What is CVE-2024-34350?

Next.js is a React framework that can provide building blocks to create web applications. Prior to 13.5.1, an inconsistent interpretation of a crafted HTTP request meant that requests are treated as both a single request, and two separate requests by Next.js, leading to desynchronized responses. This led to a response queue poisoning vulnerability in the affected Next.js versions. For a request to be exploitable, the affected route also had to be making use of the [rewrites](https://nextjs.org/docs/app/api-reference/next-config-js/rewrites) feature in Next.js. The vulnerability is resolved in Next.js `13.5.1` and newer.

Is CVE-2024-34350 actively exploited?

Active exploitation of CVE-2024-34350 has not been confirmed. Its EPSS score was 1.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-34350?

CVE-2024-34350 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running Next.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record