{"answers":{"affected":"4 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-2025-57822 exists.","fix":"Upgrade next to a fixed version for your release line: 14.2.32 or 15.4.7.","what":"CVE-2025-57822 is a medium-severity server-side request forgery vulnerability in Vercel Next.js, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-57822 and fix it if it is affected.\n\nWhat it is: CVE-2025-57822 is a medium-severity server-side request forgery vulnerability in Vercel Next.js, published on 29 Aug 2025. 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-2025-57822 exists.\n\nAffected packages and fixed versions:\n- next (npm): affected from 0.9.9; fixed in 14.2.32\n- next (npm): affected from 0.9.9; fixed in 14.2.32\n- next (npm): affected from 15.0.0-canary.0; fixed in 15.4.7\n- next (npm): affected from 15.0.0-canary.0; fixed in 15.4.7\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-2025-57822/ (Markdown: https://insights.sbomify.com/CVE-2025-57822/index.md)","id":"CVE-2025-57822","markdown":"https://insights.sbomify.com/CVE-2025-57822/index.md","name":"CVE-2025-57822","record":{"aliases":["GHSA-4342-x723-ch2f","MINI-2j35-m87x-wrqg","ROOT-APP-NPM-CVE-2025-57822"],"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 exploit improper middleware redirect handling in self-hosted Next.js apps to perform Server-Side Request Forgery.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Next.js is a React framework for building full-stack web applications. Prior to versions 14.2.32 and 15.4.7, when next() was used without explicitly passing the request object, it could lead to SSRF in self-hosted applications that incorrectly forwarded user-supplied headers. This vulnerability has been fixed in Next.js versions 14.2.32 and 15.4.7. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-57822.yaml","stars":null,"title":"Next.js Middleware - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":true,"headline":"Next.js Improper Middleware Redirect Handling Leads to SSRF","id":"CVE-2025-57822","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"ssrf","year":"2025"},"n_packages":4,"n_references":3,"next":{"headline":"Missing authorization in FortiAuthenticator","id":"CVE-2025-57823"},"packages":[{"ecosystem":"npm","fixed":["14.2.32"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-4342-x723-ch2f"},{"ecosystem":"npm","fixed":["14.2.32"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-4342-x723-ch2f"},{"ecosystem":"npm","fixed":["15.4.7"],"introduced":["15.0.0-canary.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-4342-x723-ch2f"},{"ecosystem":"npm","fixed":["15.4.7"],"introduced":["15.0.0-canary.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-4342-x723-ch2f"}],"prev":{"headline":"Basecamp's Google Sign-In for Rails allowed redirects to a malformed URL","id":"CVE-2025-57821"},"products":["next.js"],"published":"2025-08-29","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-02","vendors":["vercel"]},"summary":"Attackers can exploit improper middleware redirect handling in self-hosted Next.js apps to perform Server-Side Request Forgery.","url":"https://insights.sbomify.com/CVE-2025-57822/"}