{"answers":{"affected":"2 open source packages ship an affected version, including next. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46298 exists.","fix":"Upgrade next to 13.4.20-canary.13 or later.","what":"CVE-2023-46298 is a high-severity denial of service vulnerability in Vercel Next.js, published on 22 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46298 and fix it if it is affected.\n\nWhat it is: CVE-2023-46298 is a high-severity denial of service vulnerability in Vercel Next.js, published on 22 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46298 exists.\n\nAffected packages and fixed versions:\n- next (npm): affected from 0.9.9; fixed in 13.4.20-canary.13\n- next (npm): affected from 0.9.9; fixed in 13.4.20-canary.13\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-46298/ (Markdown: https://insights.sbomify.com/CVE-2023-46298/index.md)","id":"CVE-2023-46298","markdown":"https://insights.sbomify.com/CVE-2023-46298/index.md","name":"CVE-2023-46298","record":{"aliases":["GHSA-c59h-r6p8-q9wc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js framework","requires_auth":"none","summary":"Attackers can cause denial of service by exploiting missing cache-control headers that allow CDNs to cache empty prefetch responses.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Next.js missing cache-control header may lead to CDN caching empty reply","id":"CVE-2023-46298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"denial_of_service","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2023-46300"},"packages":[{"ecosystem":"npm","fixed":["13.4.20-canary.13"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-c59h-r6p8-q9wc"},{"ecosystem":"npm","fixed":["13.4.20-canary.13"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-c59h-r6p8-q9wc"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2023-46297"},"products":["n/a"],"published":"2023-10-22","related":[{"cvss_score":9.1,"headline":"Authorization Bypass in Next.js Middleware","id":"CVE-2025-29927","kev_date_added":null,"published":"2025-03-21"},{"cvss_score":8.6,"headline":"Next.js: Server-side request forgery in applications using WebSocket upgrades","id":"CVE-2026-44578","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":8.3,"headline":"Next.js: Server-Side Request Forgery in Image Optimization","id":"CVE-2026-94483","kev_date_added":null,"published":"2026-10-02"},{"cvss_score":8.3,"headline":"Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale","id":"CVE-2026-64642","kev_date_added":null,"published":"2026-07-27"},{"cvss_score":8.3,"headline":"Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname","id":"CVE-2026-64645","kev_date_added":null,"published":"2026-07-27"},{"cvss_score":8.3,"headline":"Next.js: Server-Side Request Forgery in Server Actions on Custom Servers","id":"CVE-2026-64649","kev_date_added":null,"published":"2026-07-27"},{"cvss_score":8.2,"headline":"Next.js: Denial of Service in App Router using Server Actions","id":"CVE-2026-64641","kev_date_added":null,"published":"2026-07-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-12","vendors":["n/a"]},"summary":"Attackers can cause denial of service by exploiting missing cache-control headers that allow CDNs to cache empty prefetch responses.","url":"https://insights.sbomify.com/CVE-2023-46298/"}