CVE-2024-46982Disclosure(vercel / next.js)

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

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

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-639

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • next.js

Threat summary

  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • General: 1 classified signal
  • Peaked 1d ago at 1 mentions (2026-03-05); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
Products
next.js

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-03-05: 1Mentions · 2026-03-12: 1Technical Details · 2026-03-05: 1Technical Details · 2026-03-12: 103-0503-12
Signal classification2 categories
Disclosure
150.0%
General
150.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-03-051
Disclosure1
2026-03-121
General1
Full discourse2 posts
  • André Baptista@0xacb
    Disclosure

    Next.js, cache, and chains: The Stale Elixir A nice work by @zhero___ This zero day brought web cache poisoning to the spotlight. His extensive research showed how source code analysis helped him craft a technique that resulted to CVE-2024-46982. Blog link 👇 https://zhero-web-sec.github.io/research-and-things/nextjs-cache-and-chains-the-stale-elixir

    Post summary

    The author highlights a newly disclosed zero‑day cache poisoning vulnerability (CVE‑2024‑46982) in Next.js, providing a research blog link.

    011084574.4K
    18.8K followersView on X
  • DailyCVE@dailycve
    General

    🔴 n8n, Remote Code Execution, #CVE-2024-46982 (Critical) https://dailycve.com/n8n-remote-code-execution-cve-2024-46982-critical/

    Post summary

    The post merely announces a CVE with a brief mention of its type and severity, offering no further technical detail or actionable information.

    0000044
    167 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appvercelnext.js-node.js-

Explore more