Service interruption via shared-response cache poisoning
Published Jul 3, 2025 · Updated Jul 8, 2025
Cache poisoning in Vercel Next.js 15.0.4-canary.51 through 15.1.7 allows remote attackers to interrupt access to static pages. The response-cache path reuses a shared response object during concurrent ISR and SSR requests, allowing an HTTP 204 status to enter the static-page cache. Exploitation requires self-hosting with cache revalidation, an SSR route, and a CDN that caches 204 responses; affected pages then return empty responses to all users.
Summary
What happened
Cache poisoning in Vercel Next.js 15.0.4-canary.51 through 15.1.7 allows remote attackers to interrupt access to static pages. The response-cache path reuses a shared response object during concurrent ISR and SSR requests, allowing an HTTP 204 status to enter the static-page cache. Exploitation requires self-hosting with cache revalidation, an SSR route, and a CDN that caches 204 responses; affected pages then return empty responses to all users.
The record
- CVE
- CVE-2025-49826
- Published
- Jul 3, 2025
- Updated
- Jul 8, 2025
- Vendor
- Vercel
- Product
- Next.js
- Classifications
- CWE-444, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 15.0.4-canary.51, < 15.1.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo