Vercel Next.js up to 15.5.28/16.4.4 App Router response splitting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.25+ |
Summary
A vulnerability marked as critical has been reported in Vercel Next.js up to 15.5.28/16.4.4. This affects an unknown function of the component App Router. The manipulation leads to response splitting. This vulnerability is traded as CVE-2026-119348. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Vercel Next.js up to 15.5.28/16.4.4 and classified as critical. This issue affects an unknown code of the component App Router. The manipulation with an unknown input leads to a response splitting vulnerability. Using CWE to declare the problem leads to CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Next.js is a React framework for building full-stack web applications. Prior to 15.5.29 and 16.4.5, self-hosted Next.js App Router route handlers and the fetch cache that return a fetched upstream response unchanged can emit a response whose declared framing does not match the body actually sent. When the application is behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients. The resulting desynchronization can inject a response into another client's queue or disclose another client's response. This issue is fixed in versions 16.4.5 and 15.5.29.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-119348 since 10/29/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 15.5.29 or 16.4.5 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 15.5.0
- 15.5.1
- 15.5.2
- 15.5.3
- 15.5.4
- 15.5.5
- 15.5.6
- 15.5.7
- 15.5.8
- 15.5.9
- 15.5.10
- 15.5.11
- 15.5.12
- 15.5.13
- 15.5.14
- 15.5.15
- 15.5.16
- 15.5.17
- 15.5.18
- 15.5.19
- 15.5.20
- 15.5.21
- 15.5.22
- 15.5.23
- 15.5.24
- 15.5.25
- 15.5.26
- 15.5.27
- 15.5.28
- 16.4.0
- 16.4.1
- 16.4.2
- 16.4.3
- 16.4.4
Website
- Product: https://github.com/vercel/next.js/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Response splittingCWE: CWE-113 / CWE-93 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Next.js 15.5.29/16.4.5
Timeline
10/29/2026 CVE reserved11/16/2026 Advisory disclosed
11/16/2026 VulDB entry created
11/16/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: GitHub_M
CVE: CVE-2026-119348 (🔒)
GCVE (CVE): GCVE-0-2026-119348
GCVE (VulDB): GCVE-100-437819
Entry
Created: 11/16/2026 20:02Changes: 11/16/2026 20:02 (68)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.