CVE-2023-46298 json
Next.js missing cache-control header may lead to CDN caching empty reply
published 2023-10-22 3 y ago modified 2026-06-17 4 mo ago also GHSA-c59h-r6p8-q9wc , EUVD-2023-2714
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN.
Patch / fix
- npm next 13.4.20-canary.13
- vercel next.js 13.4.20
- github.com/vercel/next.js@20d0595 commit
- github.com/vercel/next.js#54732 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/vercel/next.js/issues/45301 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=0.9.9, <13.4.20-canary.13 |
13.4.20-canary.13 |
Classification
- Technology feeds
References
-
github.com
/vercel/next.js/pull/54732
web, issue-tracking, patch
-
github.com
/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648
web
-
github.com
/vercel/next.js/issues/45301
web, exploit, issue-tracking, third-party-advisory
-
github.com
/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2023-46298
advisory
-
github.com
/vercel/next.js
package
Sources
- CVE List CVE-2023-46298
- GitHub Advisory GHSA-c59h-r6p8-q9wc
- NVD CVE-2023-46298
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.