{"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-44576 in the wild and no public exploit code.","fix":"Upgrade next to a fixed version for your release line: 15.5.16 or 16.2.5.","what":"CVE-2026-44576 is a medium-severity vulnerability in Vercel Next.js, published on 13 May 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-44576 and fix it if it is affected.\n\nWhat it is: CVE-2026-44576 is a medium-severity vulnerability in Vercel Next.js, published on 13 May 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-44576 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next (npm): affected from 14.2.0; fixed in 15.5.16\n- next (npm): affected from 14.2.0; fixed in 15.5.16\n- next (npm): affected from 16.0.0; fixed in 16.2.5\n- next (npm): affected from 16.0.0; fixed in 16.2.5\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-44576/ (Markdown: https://insights.sbomify.com/CVE-2026-44576/index.md)","id":"CVE-2026-44576","markdown":"https://insights.sbomify.com/CVE-2026-44576/index.md","name":"CVE-2026-44576","record":{"aliases":["CLEANSTART-2026-GL78918","CLEANSTART-2026-ML50911","GHSA-wfc6-r584-vfw7","MINI-f6rj-93mg-w2f4","MINI-hg8x-q5hj-m4h4","MINI-hrwg-5fq8-3qx2","MINI-xrmm-xxvg-f3c2","ROOT-APP-NPM-CVE-2026-44576"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Next.js framework","requires_auth":"none","summary":"Attackers can poison shared caches to serve incorrect React Server Component payloads to visitors, requiring specific cache partitioning configurations.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"Next.js is a React framework for building full-stack web applications. From 14.2.0 to before 15.5.16 and 16.2.5, applications using React Server Components can be vulnerable to cache poisoning when shared caches do not correctly partition response variants. Under affected conditions, an attacker can cause an RSC response to be served from the original URL and poison shared cache entries so later visitors receive component payloads instead of the expected HTML. This vulnerability is fixed in 15.5.16 and 16.2.5.","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 poisoning in React Server Component responses","id":"CVE-2026-44576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"other","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Next.js: Denial of Service in the Image Optimization API","id":"CVE-2026-44577"},"packages":[{"ecosystem":"npm","fixed":["15.5.16"],"introduced":["14.2.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-wfc6-r584-vfw7"},{"ecosystem":"npm","fixed":["15.5.16"],"introduced":["14.2.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-wfc6-r584-vfw7"},{"ecosystem":"npm","fixed":["16.2.5"],"introduced":["16.0.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-wfc6-r584-vfw7"},{"ecosystem":"npm","fixed":["16.2.5"],"introduced":["16.0.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-wfc6-r584-vfw7"}],"prev":{"headline":"Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes","id":"CVE-2026-44575"},"products":["next.js"],"published":"2026-05-13","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-05-18","vendors":["vercel"]},"summary":"Attackers can poison shared caches to serve incorrect React Server Component payloads to visitors, requiring specific cache partitioning configurations.","url":"https://insights.sbomify.com/CVE-2026-44576/"}