{"answers":{"affected":"2 open source packages ship an affected version, including next. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-103004 in the wild and no public exploit code.","fix":"Upgrade next to 16.3.8 or later.","what":"CVE-2026-103004 is a medium-severity vulnerability in Vercel Next.js, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103004 and fix it if it is affected.\n\nWhat it is: CVE-2026-103004 is a medium-severity vulnerability in Vercel Next.js, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103004 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next (npm): affected from 16.3.0; fixed in 16.3.8\n- next (npm): affected from 16.3.0; fixed in 16.3.8\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-103004/ (Markdown: https://insights.sbomify.com/CVE-2026-103004/index.md)","id":"CVE-2026-103004","markdown":"https://insights.sbomify.com/CVE-2026-103004/index.md","name":"CVE-2026-103004","record":{"aliases":["CLEANSTART-2026-MS47438","CLEANSTART-2026-SE76644","GHSA-h694-7cp9-m8p3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Next.js framework","requires_auth":"none","summary":"Next.js cache keying flaw allows leaking cached content across different root parameters when Cache Components are enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/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 versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further.\n\nWhat values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first.\n\nThis has been patched in 16.3.8.","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 cache leak on warm `use cache` handlers accessing root param","id":"CVE-2026-103004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Memory Allocation with Excessive Size Value in Elasticsearch Leading to Denial of Service","id":"CVE-2026-103005"},"packages":[{"ecosystem":"npm","fixed":["16.3.8"],"introduced":["16.3.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-h694-7cp9-m8p3"},{"ecosystem":"npm","fixed":["16.3.8"],"introduced":["16.3.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-h694-7cp9-m8p3"}],"prev":{"headline":"PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse","id":"CVE-2026-103001"},"products":["next.js"],"published":"2026-10-01","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["vercel"]},"summary":"Next.js cache keying flaw allows leaking cached content across different root parameters when Cache Components are enabled.","url":"https://insights.sbomify.com/CVE-2026-103004/"}