Next.js missing cache-control header may lead to CDN caching empty reply
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. Cloudflare considers these requests cacheable assets.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | next | >= 0.9.9, < 13.4.20-canary.13 | 13.4.20-canary.13 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2023-46298
- https://github.com/vercel/next.js/issues/45301
- https://github.com/vercel/next.js/pull/54732
- https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648
- https://github.com/vercel/next.js
- https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13
- Weakness (CWE)
-- Platform
- npm
- Package
next- Disclosed
- 22.10.2023
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-c59h-r6p8-q9wc - CC BY 4.0
Vulnerability history: next
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 73
- First → latest
- 12.2017 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 5
- High 27
- Medium 32
- Low 9
Disclosures per year
- 2017: 1
- 2018: 2
- 2019: 0
- 2020: 3
- 2021: 3
- 2022: 3
- 2023: 1
- 2024: 6
- 2025: 14
- 2026: 40
-
Next.js missing cache-control header may lead to CDN caching empty reply this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.