{"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-64644 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-64644 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 27 Jul 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-64644 and fix it if it is affected.\n\nWhat it is: CVE-2026-64644 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 27 Jul 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-64644 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next (npm): affected from 15.5.0; fixed in 15.5.21\n- next (npm): affected from 15.5.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-64644/ (Markdown: https://insights.sbomify.com/CVE-2026-64644/index.md)","id":"CVE-2026-64644","markdown":"https://insights.sbomify.com/CVE-2026-64644/index.md","name":"CVE-2026-64644","record":{"aliases":["CLEANSTART-2026-LH73622","CLEANSTART-2026-VX56727","ECHO-4e9d-a9c7-9b65","GHSA-q8wf-6r8g-63ch","MINI-89cg-hj9f-5w3x","MINI-9fph-3qg3-8hrr","MINI-cv46-f52x-7fg9","MINI-jf4f-w5r9-4jvw","ROOT-APP-NPM-CVE-2026-64644"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Next.js framework","requires_auth":"none","summary":"Attackers can cause CPU exhaustion in Next.js Image Optimization API via malicious remote SVGs when remote image optimization is enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"Next.js is a React framework for building full-stack web applications. In versions 15.5.0 through 15.5.20 and 16.0.0 through 16.2.10, when self-hosting Next.js with the default image loader, the Image Optimization API can optimize remotely hosted images if configured (not enabled by default). If those images contain malicious content, they can cause CPU exhaustion in /_next/image endpoints.Only config.images.remotePatterns is affected, and just the patterns in that array, whereas config.images.unoptimized: true, config.images.loader: 'custom', and Vercel are not impacted. 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: Denial of Service in the Image Optimization API using SVGs","id":"CVE-2026-64644","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"denial_of_service","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname","id":"CVE-2026-64645"},"packages":[{"ecosystem":"npm","fixed":["15.5.21"],"introduced":["15.5.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-q8wf-6r8g-63ch"},{"ecosystem":"npm","fixed":["15.5.21"],"introduced":["15.5.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-q8wf-6r8g-63ch"},{"ecosystem":"npm","fixed":["16.2.11"],"introduced":["16.0.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-q8wf-6r8g-63ch"},{"ecosystem":"npm","fixed":["16.2.11"],"introduced":["16.0.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-q8wf-6r8g-63ch"}],"prev":{"headline":"Next.js: Unauthenticated Disclosure of Internal Server Function endpoints","id":"CVE-2026-64643"},"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-27","vendors":["vercel"]},"summary":"Attackers can cause CPU exhaustion in Next.js Image Optimization API via malicious remote SVGs when remote image optimization is enabled.","url":"https://insights.sbomify.com/CVE-2026-64644/"}