CVE-2024-46982

HIGH EXPLOITED

Next.js 13.5.1-13.5.6 and 14.2.1-14.2.9 - Cache Poisoning via Crafted HTTP Request

Title source: llm
STIX 2.1

Exploitation Summary

CVE-2024-46982 has been observed exploited in the wild (reported by VulnCheck KEV). EIP tracks 5 public exploits from researchers including Lercas, hidesec, samuel871211.

AI-analyzed exploit summary This Go-based exploit automates the detection and exploitation of CVE-2024-46982, a cache poisoning vulnerability in Next.js where SSR responses can be incorrectly cached as SSG. It injects payloads via the User-Agent header and checks for reflection in responses.

Description

Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a `Cache-Control: s-maxage=1, stale-while-revalidate` header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx`. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Exploits (5)

nomisec WORKING POC 3 stars
by Lercas · client-side
https://github.com/Lercas/CVE-2024-46982

This Go-based exploit automates the detection and exploitation of CVE-2024-46982, a cache poisoning vulnerability in Next.js where SSR responses can be incorrectly cached as SSG. It injects payloads via the User-Agent header and checks for reflection in responses.

Classification
Working Poc 90%
Attack Type
Xss
Complexity
Moderate
Reliability
Reliable
Target: Next.js (versions affected by CVE-2024-46982)
No auth needed
Prerequisites: List of target URLs · Payloads for injection via User-Agent header
devstral-2 · analyzed Feb 16, 2026 Full analysis →
nomisec WORKING POC 1 stars
by hidesec · infoleak
https://github.com/hidesec/CVE-2025-32421

This repository contains a working proof-of-concept for CVE-2025-32421, demonstrating a race condition attack against Next.js 15.0.4 that bypasses the CVE-2024-46982 patch to expose sensitive server-side data.

Classification
Working Poc 95%
Attack Type
Info Leak
Complexity
Moderate
Reliability
Reliable
Target: Next.js 15.0.4
No auth needed
Prerequisites: Next.js 15.0.4 application running · Network access to the target
devstral-2 · analyzed Feb 16, 2026 Full analysis →
nomisec WORKING POC
by samuel871211 · client-side
https://github.com/samuel871211/CVE-2024-46982-Reproduction

This repository demonstrates a stored XSS vulnerability in Next.js via cache poisoning. The exploit leverages custom headers and query strings to manipulate caching behavior, allowing malicious scripts to be stored and executed in the context of other users' sessions.

Classification
Working Poc 95%
Attack Type
Xss
Complexity
Moderate
Reliability
Reliable
Target: Next.js (version not specified)
No auth needed
Prerequisites: Node.js LTS installed · Next.js application running locally or remotely · Ability to send crafted HTTP requests
devstral-2 · analyzed Feb 16, 2026 Full analysis →
nomisec STUB
by melmathari · poc
https://github.com/melmathari/CVE-2024-46982-NUCLEI

This repository appears to be a basic Next.js template without any exploit code or vulnerability details for CVE-2024-46982. It lacks PoC logic or offensive techniques.

Classification
Stub 90%
Attack Type
Other
Complexity
Trivial
Reliability
Theoretical
Target: Unknown (Next.js template only)
No auth needed
Prerequisites: None identified
devstral-2 · analyzed Feb 16, 2026 Full analysis →
nomisec WORKING POC
by CodePontiff · client-side
https://github.com/CodePontiff/next_js_poisoning

This PoC demonstrates a cache poisoning vulnerability in Next.js by uploading multiple copies of an image via the `_next/image?url=` endpoint, bypassing protections with delays. It leverages attacker-controlled URLs to poison the victim's cache.

Classification
Working Poc 90%
Attack Type
Other
Complexity
Moderate
Reliability
Reliable
Target: Next.js versions 13.5.1 to 13.5.7 and 14.0.0 to 14.2.10
No auth needed
Prerequisites: Attacker-controlled server (e.g., Ngrok/Apache) · Victim Next.js instance with vulnerable `_next/image` endpoint
devstral-2 · analyzed Feb 16, 2026 Full analysis →

Scores

CVSS v3 7.5
EPSS 0.4906
EPSS Percentile 97.8%
Attack Vector NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CISA SSVC

Vulnrichment
Exploitation none
Automatable yes
Technical Impact partial

Details

VulnCheck KEV 2025-06-08
CWE
CWE-639
Status published
Products (2)
npm/next 13.5.1 - 13.5.7npm
vercel/next.js 13.5.1 - 13.5.7
Published Sep 17, 2024
Tracked Since Feb 18, 2026