Chainvercel · next.jsnpm:next
vercel next.js: successive fixes (2023–2025)
6 CVEs over 5 generations, 22 Oct 2023 to 29 Aug 2025.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2023-4629822 Oct 2023 First in the chain
- CVE-2024-4698217 Sep 2024 related to CVE-2023-46298
- CVE-2024-5147917 Dec 2024 related to CVE-2024-46982related to CVE-2023-46298
- CVE-2025-490053 Jul 2025 related to CVE-2023-46298related to CVE-2024-46982and 1 more
- CVE-2025-498263 Jul 2025 related to CVE-2023-46298related to CVE-2024-46982and 2 more
- CVE-2025-5782229 Aug 2025 related to CVE-2024-51479
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2023-46298 | 22 Oct 2023 | Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be… · fixed in 13.4.20-canary.13 | First in chain | 15.2 |
| CVE-2024-46982 | 17 Sep 2024 | Cache Poisoning in next.js · fixed in 14.2.10 | CVE-2023-46298 · related · Medium | 65.1 |
| CVE-2024-51479 | 17 Dec 2024 | Authorization bypass in Next.js · fixed in 14.2.15 | CVE-2024-46982 · related · High | 23.4 |
| CVE-2025-49005 | 3 Jul 2025 | Next.js cache poisoning due to omission of Vary header · fixed in 15.3.3 | CVE-2023-46298 · related · Medium | 11.0 |
| CVE-2025-49826 | 3 Jul 2025 | Next.js DoS vulnerability via cache poisoning · fixed in 15.1.8 | CVE-2023-46298 · related · Medium | 18.5 |
| CVE-2025-57822 | 29 Aug 2025 | Next.js Improper Middleware Redirect Handling Leads to SSRF · fixed in 15.4.7 | CVE-2024-51479 · related · Medium | 26.6 |