Skip to content
OpenAdvisories
Low · 3.7 CVE-2025-49005 EUVD-2025-19911GHSA-r2fc-ccr8-96c4

Next.js cache poisoning due to omission of Vary header

Published Jul 3, 2025 · Updated Jul 8, 2025 · Assigned by GitHub_M

Description

Next.js is a React framework for building full-stack web applications. In Next.js App Router from 15.3.0 to before 15.3.3 and Vercel CLI from 41.4.1 to 42.2.0, a cache poisoning vulnerability was found. The issue allowed page requests for HTML content to return a React Server Component (RSC) payload instead under certain conditions. When deployed to Vercel, this would only impact the browser cache, and would not lead to the CDN being poisoned. When self-hosted and deployed externally, this could lead to cache poisoning if the CDN does not properly distinguish between RSC / HTML in the cache keys. This issue has been resolved in Next.js 15.3.3.

Affected products

VendorProductAffectedFixed
vercel next.js >= 15.3.0, < 15.3.3 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling jitsucom-jitsu +2 2.10.0-r2 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm next >= 15.3.0, < 15.3.3 15.3.3 GHSA-r2fc-ccr8-96c4

Advisories 1

References