{"answers":{"affected":"2 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-2024-34351 exists.","fix":"Upgrade next to 14.1.1 or later.","what":"CVE-2024-34351 is a high-severity server-side request forgery vulnerability in Vercel Next.js, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-34351 and fix it if it is affected.\n\nWhat it is: CVE-2024-34351 is a high-severity server-side request forgery vulnerability in Vercel Next.js, published on 9 May 2024. 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-2024-34351 exists.\n\nAffected packages and fixed versions:\n- next (npm): affected from 13.4.0; fixed in 14.1.1\n- next (npm): affected from 13.4.0; fixed in 14.1.1\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-2024-34351/ (Markdown: https://insights.sbomify.com/CVE-2024-34351/index.md)","id":"CVE-2024-34351","markdown":"https://insights.sbomify.com/CVE-2024-34351/index.md","name":"CVE-2024-34351","record":{"aliases":["GHSA-fr5h-rqp8-mj6g","MINI-fjrc-v88x-336m","ROOT-APP-NPM-CVE-2024-34351"],"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 SSRF in Next.js Server Actions by modifying the Host header, allowing requests from the server if specific redirect conditions are met.","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":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the `Host` header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a `/`. This vulnerability was fixed in Next.js `14.1.1`.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2024-05-12","github_poc":4,"max_poc_stars":10,"metasploit":0,"nuclei":1,"refs":[{"date":"2024-05-12T10:49:41Z","kind":"github_poc","ref":"https://github.com/Voorivex/CVE-2024-34351","stars":10,"title":null},{"date":"2024-08-27T15:10:26Z","kind":"github_poc","ref":"https://github.com/God4n/nextjs-CVE-2024-34351-_exploit","stars":9,"title":"PoC for a full exploitation of NextJS SSRF (CVE-2024-34351)"},{"date":"2024-06-11T13:19:18Z","kind":"github_poc","ref":"https://github.com/avergnaud/Next.js_exploit_CVE-2024-34351","stars":1,"title":null},{"date":"2026-04-12T17:26:55Z","kind":"github_poc","ref":"https://github.com/Jinlei-Chen-UWO/cve-2024-34351-demo","stars":0,"title":null},{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-34351.yaml","stars":null,"title":"Next.js - Server Side Request Forgery (SSRF)"}],"tier":"weaponised"},"has_fix":true,"headline":"Next.js Server-Side Request Forgery in Server Actions","id":"CVE-2024-34351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"ssrf","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Arbitrary file write vulnerability in 1Panel","id":"CVE-2024-34352"},"packages":[{"ecosystem":"npm","fixed":["14.1.1"],"introduced":["13.4.0"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-fr5h-rqp8-mj6g"},{"ecosystem":"npm","fixed":["14.1.1"],"introduced":["13.4.0"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-fr5h-rqp8-mj6g"}],"prev":{"headline":"Next.js Vulnerable to HTTP Request Smuggling","id":"CVE-2024-34350"},"products":["next.js"],"published":"2024-05-09","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"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["vercel"]},"summary":"Attackers can exploit SSRF in Next.js Server Actions by modifying the Host header, allowing requests from the server if specific redirect conditions are met.","url":"https://insights.sbomify.com/CVE-2024-34351/"}