Skip to content
Vulnerability Intelligence

CVE-2024-46982

HighExploited

Next.js Cache Poisoning

Published Sep 17, 2024 · Updated Sep 21, 2026 · Also known as GHSA-gp8f-8m3g-qvj9, ROOT-APP-NPM-CVE-2024-46982

Key Facts

Patch immediately
  • CVE-2024-46982 is a high-severity vulnerability (CVSS 8.7 v4) affecting Next.js (Vercel), jitsucom-jitsu (chainguard), trigger-dev (minimos) and 3 more products.
  • It is exploited in the wild, listed in Industry KEV feed since Jun 8, 2025. No public exploit code is known.
  • EPSS estimates a 59% probability of exploitation in the next 30 days.
  • Fixed versions are available, including @rootio/next 13.5.4-root.io.2, @rootio/next 13.5.4-root.io.3, @rootio/next 13.5.4-root.io.4.
  • Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v4

8.7

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

EPSS (30-day exploit likelihood)

59%

Higher than 99.1% of all scored CVEs

Exploited in the wild

Yes

1 catalog listing

Public exploit code

None known

Get the full CVE-2024-46982 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

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.

Known-Exploited Catalog Listings

CatalogAddedRemediation dueRansomware use
Industry KEV feedJun 8, 2025n/aNot reported

Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected Products

9 affected entries in total
ProductAffected versionsFixed in
Next.jsVercel>= >= 13.5.1, < 13.5.713.5.7
jitsucom-jitsuchainguardSee advisory2.8.2-r1
trigger-devminimosSee advisory4.5.0-r0
nextnpm>= 13.5.113.5.7
vercel/next.jsgithub-repoSee advisoryn/a
1 more affected products in the full CVE brief

Patched Releases

@rootio/next

13.5.4-root.io.2, 13.5.4-root.io.3, 13.5.4-root.io.4, 13.5.4-root.io.5, 13.5.4-root.io.6, 13.5.6-root.io.2, 13.5.6-root.io.3, 13.5.6-root.io.4, 13.5.6-root.io.5, 13.5.6-root.io.6, 13.5.6-root.io.7, 14.0.0-root.io.3, 14.0.0-root.io.4, 14.0.0-root.io.5, 14.0.0-root.io.6, 14.0.0-root.io.7, 14.0.3-root.io.2, 14.0.3-root.io.3, 14.0.3-root.io.4, 14.0.3-root.io.5, 14.0.3-root.io.6, 14.0.4-root.io.2, 14.0.4-root.io.3, 14.0.4-root.io.4, 14.0.4-root.io.5, 14.0.4-root.io.6, 14.0.4-root.io.7, 14.0.4-root.io.8, 14.0.4-root.io.9, 14.1.0-root.io.3, 14.1.0-root.io.4, 14.1.0-root.io.5, 14.1.0-root.io.6, 14.1.0-root.io.7, 14.1.0-root.io.8, 14.1.3-root.io.1, 14.1.3-root.io.2, 14.1.3-root.io.3, 14.1.3-root.io.4, 14.1.3-root.io.5, 14.1.3-root.io.6, 14.1.3-root.io.7, 14.1.3-root.io.8, 14.1.4-root.io.5, 14.1.4-root.io.6, 14.1.4-root.io.7, 14.1.4-root.io.8, 14.1.4-root.io.9, 14.2.0-root.io.1, 14.2.0-root.io.2, 14.2.0-root.io.3, 14.2.0-root.io.4, 14.2.0-root.io.5, 14.2.0-root.io.6, 14.2.10-root.io.1, 14.2.10-root.io.2, 14.2.10-root.io.3, 14.2.10-root.io.4, 14.2.2-root.io.7, 14.2.2-root.io.8, 14.2.2-root.io.9, 14.2.3-root.io.2, 14.2.3-root.io.3, 14.2.3-root.io.4, 14.2.3-root.io.5, 14.2.5-root.io.10, 14.2.5-root.io.2, 14.2.5-root.io.3, 14.2.5-root.io.4, 14.2.5-root.io.5, 14.2.5-root.io.6, 14.2.5-root.io.7, 14.2.5-root.io.8, 14.2.5-root.io.9

jitsucom-jitsu

2.8.2-r1

next

13.5.4-aikido.2, 13.5.4-aikido.3, 13.5.4-aikido.4, 13.5.4-aikido.5, 13.5.4-aikido.6, 13.5.6-aikido.2, 13.5.6-aikido.3, 13.5.6-aikido.4, 13.5.6-aikido.5, 13.5.6-aikido.6, 13.5.6-aikido.7, 13.5.7, 14.0.0-aikido.3, 14.0.0-aikido.4, 14.0.0-aikido.5, 14.0.0-aikido.6, 14.0.0-aikido.7, 14.0.3-aikido.2, 14.0.3-aikido.3, 14.0.3-aikido.4, 14.0.3-aikido.5, 14.0.3-aikido.6, 14.0.4-aikido.2, 14.0.4-aikido.3, 14.0.4-aikido.4, 14.0.4-aikido.5, 14.0.4-aikido.6, 14.0.4-aikido.7, 14.0.4-aikido.8, 14.0.4-aikido.9, 14.1.0-aikido.3, 14.1.0-aikido.4, 14.1.0-aikido.5, 14.1.0-aikido.6, 14.1.0-aikido.7, 14.1.0-aikido.8, 14.1.3-aikido.1, 14.1.3-aikido.2, 14.1.3-aikido.3, 14.1.3-aikido.4, 14.1.3-aikido.5, 14.1.3-aikido.6, 14.1.3-aikido.7, 14.1.3-aikido.8, 14.1.4-aikido.5, 14.1.4-aikido.6, 14.1.4-aikido.7, 14.1.4-aikido.8, 14.1.4-aikido.9, 14.2.0-aikido.1, 14.2.0-aikido.2, 14.2.0-aikido.3, 14.2.0-aikido.4, 14.2.0-aikido.5, 14.2.0-aikido.6, 14.2.10, 14.2.10-aikido.1, 14.2.10-aikido.2, 14.2.10-aikido.3, 14.2.10-aikido.4, 14.2.2-aikido.7, 14.2.2-aikido.8, 14.2.2-aikido.9, 14.2.3-aikido.2, 14.2.3-aikido.3, 14.2.3-aikido.4, 14.2.3-aikido.5, 14.2.5-aikido.10, 14.2.5-aikido.2, 14.2.5-aikido.3, 14.2.5-aikido.4, 14.2.5-aikido.5, 14.2.5-aikido.6, 14.2.5-aikido.7, 14.2.5-aikido.8, 14.2.5-aikido.9

trigger-dev

4.5.0-r0

Next.js

13.5.7

Timeline

  1. Publicly disclosed

    Sep 17, 2024

  2. Added to Industry KEV feed

    Jun 8, 2025

  3. Last updated

    Sep 21, 2026

Weakness Type

  • CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

4 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2024-46982 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo