{"answers":{"affected":"2 open source packages ship an affected version, including next. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-37699 in the wild and no public exploit code.","fix":"Upgrade next to 11.1.0 or later.","what":"CVE-2021-37699 is a medium-severity vulnerability in Vercel Next.js, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-37699 and fix it if it is affected.\n\nWhat it is: CVE-2021-37699 is a medium-severity vulnerability in Vercel Next.js, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-37699 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next (npm): affected from 0.9.9; fixed in 11.1.0\n- next (npm): affected from 0.9.9; fixed in 11.1.0\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-2021-37699/ (Markdown: https://insights.sbomify.com/CVE-2021-37699/index.md)","id":"CVE-2021-37699","markdown":"https://insights.sbomify.com/CVE-2021-37699/index.md","name":"CVE-2021-37699","record":{"aliases":["GHSA-vxf5-wxwp-m7g9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js framework","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via specially encoded paths in statically generated error pages, facilitating phishing attacks.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain. We recommend everyone to upgrade regardless of whether you can reproduce the issue or not. The issue has been patched in release 11.1.0.","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":"Open Redirect in Next.js versions below 11.1.0","id":"CVE-2021-37699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"open_redirect","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Clipboard-based DOM-XSS","id":"CVE-2021-37700"},"packages":[{"ecosystem":"npm","fixed":["11.1.0"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-vxf5-wxwp-m7g9"},{"ecosystem":"npm","fixed":["11.1.0"],"introduced":["0.9.9"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-vxf5-wxwp-m7g9"}],"prev":{"headline":"Missing TLS service certificate validation in GelfWriter, ElasticsearchWriter, InfluxdbWriter and Influxdb2Writer","id":"CVE-2021-37698"},"products":["next.js"],"published":"2021-08-11","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["vercel"]},"summary":"Attackers can redirect users to malicious sites via specially encoded paths in statically generated error pages, facilitating phishing attacks.","url":"https://insights.sbomify.com/CVE-2021-37699/"}