Redirect-path denial of service via trusted external header
Published May 13, 2026 · Updated May 13, 2026
Cache poisoning in Vercel Next.js 12.2.0 through 15.5.15 and 16.0.0 through 16.2.4 allows remote attackers to disrupt redirect paths. Middleware redirect handling accepts the external x-nextjs-data header as proof of an internal data request and replaces Location with x-nextjs-redirect. Exploitation requires a middleware or proxy redirect behind a cache that stores 3xx responses without distinguishing internal data requests.
Summary
What happened
Cache poisoning in Vercel Next.js 12.2.0 through 15.5.15 and 16.0.0 through 16.2.4 allows remote attackers to disrupt redirect paths. Middleware redirect handling accepts the external x-nextjs-data header as proof of an internal data request and replaces Location with x-nextjs-redirect. Exploitation requires a middleware or proxy redirect behind a cache that stores 3xx responses without distinguishing internal data requests.
The record
- CVE
- CVE-2026-44572
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Vercel
- Product
- Next.js
- Classifications
- CWE-349, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record 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=>= 12.2.0, < 15.5.16
- Affected versionversion=>= 16.0.0, < 16.2.5
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