CVE-2024-34350

Next.js Vulnerable to HTTP Request Smuggling

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.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.90% Top 30%
Affected: vercel next.js
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2024-34350?
CVE-2024-34350 has been scored as a high severity vulnerability.
How to fix CVE-2024-34350?
To fix CVE-2024-34350, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-34350 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-34350 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-34350?
CVE-2024-34350 affects vercel next.js.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.