next is vulnerable to Cache Poisoning
37
CVE Score
Low
Cache Poisoning
Middleware redirect handling can trust externally supplied internal-data headers in affected deployments. A crafted request can alter redirect response shape and poison cached redirect entries when caches do not partition on this signal. Subsequent users can receive unusable cached redirects until expiry. The fix requires validated internal routing state before treating requests as internal data requests.
Upgrade the next library to the patch version.
You are affected if you are using a version that falls within the vulnerable range.
12.2.0 - 15.5.15
Fixed in 15.5.1616.0.0 - 16.2.4
Fixed in 16.2.5next is vulnerable to Cache Poisoning in versions 12.2.0 - 15.5.15 and 16.0.0 - 16.2.4.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.