{"answers":{"affected":"4 open source packages ship an affected version, including next. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64648 in the wild and no public exploit code.","fix":"Upgrade next to a fixed version for your release line: 15.5.21 or 16.2.11.","what":"CVE-2026-64648 is a medium-severity vulnerability in Vercel Next.js, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-64648 and fix it if it is affected.\n\nWhat it is: CVE-2026-64648 is a medium-severity vulnerability in Vercel Next.js, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-64648 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next (npm): affected from 13.0.0; fixed in 15.5.21\n- next (npm): affected from 13.0.0; fixed in 15.5.21\n- next (npm): affected from 16.0.0; fixed in 16.2.11\n- next (npm): affected from 16.0.0; fixed in 16.2.11\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-2026-64648/ (Markdown: https://insights.sbomify.com/CVE-2026-64648/index.md)","id":"CVE-2026-64648","markdown":"https://insights.sbomify.com/CVE-2026-64648/index.md","name":"CVE-2026-64648","record":{"aliases":["CLEANSTART-2026-CT47808","CLEANSTART-2026-FH10716","ECHO-0963-68f9-9ca4","GHSA-68g3-v927-f742","MINI-p66g-q6g3-98cv","MINI-qrg7-jc4m-8jcx","MINI-rc6c-47jc-v46p","MINI-v9x2-87f5-fhmv","ROOT-APP-NPM-CVE-2026-64648"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js framework","requires_auth":"none","summary":"Server-side fetch caching confusion may leak confidential response data from one request to another unauthorized request in Next.js applications.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"description":"Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a  server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Next.js: Response Body Cache Confusion for Requests Containing Bodies","id":"CVE-2026-64648","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Next.js: Server-Side Request Forgery in Server Actions on Custom Servers","id":"CVE-2026-64649"},"packages":[{"ecosystem":"npm","fixed":["15.5.21"],"introduced":["13.0.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-68g3-v927-f742"},{"ecosystem":"npm","fixed":["15.5.21"],"introduced":["13.0.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-68g3-v927-f742"},{"ecosystem":"npm","fixed":["16.2.11"],"introduced":["16.0.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-68g3-v927-f742"},{"ecosystem":"npm","fixed":["16.2.11"],"introduced":["16.0.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-68g3-v927-f742"}],"prev":{"headline":"Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies","id":"CVE-2026-64647"},"products":["next.js"],"published":"2026-07-27","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["vercel"]},"summary":"Server-side fetch caching confusion may leak confidential response data from one request to another unauthorized request in Next.js applications.","url":"https://insights.sbomify.com/CVE-2026-64648/"}