Vercel Next.js up to 15.5.26/16.3.7 Cache denial of service

Summaryinfo

A vulnerability, which was classified as critical, has been found in Vercel Next.js up to 15.5.26/16.3.7. This vulnerability affects unknown code of the component Cache. The manipulation leads to denial of service. This vulnerability is documented as CVE-2026-94484. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Vercel Next.js up to 15.5.26/16.3.7 and classified as critical. This issue affects an unknown functionality of the component Cache. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes can use a shared response cache key that is insufficiently scoped to the source route. A single unauthenticated crafted request can poison that cache, causing cross-user content substitution or persistent denial of service until the poisoned entry is revalidated or replaced. This issue is fixed in versions 15.5.27 and 16.3.8.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-94484 since 09/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 15.5.27 or 16.3.8 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• JavaScript Library

Vendor

• Vercel

Name

• Next.js

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
• 16.3.0
• 16.3.1
• 16.3.2
• 16.3.3
• 16.3.4
• 16.3.5
• 16.3.6
• 16.3.7

Website

• Product: https://github.com/vercel/next.js/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion