CVE-2023-46298
unknown
CVSS v3
—
CVSS v4 NEW
—
VIR risk
—
Description
Next.js missing cache-control header may lead to CDN caching empty reply
Predictions
Exploit likelihood
20%
Patch ETA
—
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| npm | 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
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.