Vulnerability in Vercel Next.js
CVE-2023-46298
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS: 0.013 (69.0th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 69th percentile — 69.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.013 · newest: 0.013 · change: 0.000
Affected products
- Vercel Next.js — versions 13.4.20
Public proof-of-concept exploits
References
- github.com/vercel/next.js/pull/54732 (Patch, Issue Tracking)
- github.com/vercel/next.js/issues/45301 (Exploit, Third Party Advisory, Issue Tracking)
- github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13 (Product)
Frequently asked questions
- What is CVE-2023-46298?
- CVE-2023-46298 is a high-severity vulnerability in Vercel Next.js. CVSS score: 7.5/10. Published 2023-10-22.
- How severe is CVE-2023-46298?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2023-46298 known to be exploited?
- 10 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.