# CVE-2024-46982: Next.js - Cache Poisoning

> Live exploitation tracking for CVE-2024-46982 by the CrowdSec Live Exploit Tracker, built from real-world attack data crowdsourced from CrowdSec's global network.

Page: https://tracker.crowdsec.net/cves/CVE-2024-46982

## Key facts

- **Exploitation phase:** Limited Exploitation. The vulnerability is known but shows very limited attacker interest or exploitation activity.
- **CVSS score:** 7.5
- **Public exploit available:** Yes
- **Affected products:** Vercel Next.js
- **Weaknesses:** CWE-639 (Authorization Bypass Through User-Controlled Key)
- **Tags:** web_application

## 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.

## CrowdSec analysis

[CVE-2024-46982](https://euvd.enisa.europa.eu/vulnerability/CVE-2024-46982) is a vulnerability in Next.js that allows cache poisoning of certain server-side rendered routes. By sending a specially crafted HTTP request, attackers can coerce affected configurations to improperly cache responses, potentially serving cached data to unintended users or through upstream CDNs.

CrowdSec has been tracking this vulnerability and its exploits since 5th of March 2025.

CrowdSec has not observed any significant exploitation activity targeting CVE-2024-46982 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.

Exploitation attempts, when detected, will typically target URLs containing the `?__nextdatareq=1` pattern.

## Timeline

- 2024-09-17: CVE Published. CVE-2024-46982 is published to NVD.
- 2025-03-05: Rule Released. CrowdSec releases a rule to detect CVE-2024-46982 exploitation attempts against the CrowdSec Network.
- 2025-03-14: CrowdSec First Seen. CrowdSec observes in-the-wild exploitation of CVE-2024-46982 for the first time.

## References

- https://github.com/vercel/next.js/security/advisories/GHSA-gp8f-8m3g-qvj9
- https://github.com/vercel/next.js/commit/7ed7f125e07ef0517a331009ed7e32691ba403d3
- https://github.com/vercel/next.js/commit/bd164d53af259c05f1ab434004bcfdd3837d7cda

## Live exploitation data

The [Live Exploit Tracker page](https://tracker.crowdsec.net/cves/CVE-2024-46982) follows observed exploitation activity for CVE-2024-46982. [Request an API key](https://tracker.crowdsec.net/request-api-key) for full access to its exploitation timeline, attacking IP addresses and blocklists.