AIKIDO-2026-206850
next is vulnerable to Sensitive Information Disclosure
60
Medium Risk
This Affects:
nextTL;DR
Next.js deduplicates and caches server-side fetch responses using a cache key that does not fully account for the request body. When fetch is called with a Request whose init differs from the init passed directly to fetch, a request to the same URL with a different body can receive a response body cached from another request. Confidential data contained in one POST response can therefore be served to unauthorized callers. The fix incorporates the request body into the cache key so responses are no longer confused. Applications using the Pages Router are not affected.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and your application uses the App Router with server-side fetch calls where the Request init differs from the init passed to fetch.
Background info
next is vulnerable to Sensitive Information Disclosure in versions 13.0.0 - 15.5.20 and 16.0.0 - 16.2.10.
How to fix this
Upgrade the next library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant