{"answers":{"affected":"2 open source packages ship an affected version, including next. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27978 in the wild and no public exploit code.","fix":"Upgrade next to 16.1.7 or later.","what":"CVE-2026-27978 is a medium-severity vulnerability in Vercel Next.js, published on 17 Mar 2026. 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-2026-27978 and fix it if it is affected.\n\nWhat it is: CVE-2026-27978 is a medium-severity vulnerability in Vercel Next.js, published on 17 Mar 2026. 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-2026-27978 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next (npm): affected from 16.0.1; fixed in 16.1.7\n- next (npm): affected from 16.0.1; fixed in 16.1.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-2026-27978/ (Markdown: https://insights.sbomify.com/CVE-2026-27978/index.md)","id":"CVE-2026-27978","markdown":"https://insights.sbomify.com/CVE-2026-27978/index.md","name":"CVE-2026-27978","record":{"aliases":["GHSA-mq59-m269-xvcx","MINI-c5hg-9ww7-fp9h","MINI-hrwq-7pv7-87hw","ROOT-APP-NPM-CVE-2026-27978"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js framework","requires_auth":"none","summary":"Attackers can bypass Server Action CSRF checks using null origins from sandboxed iframes, allowing state-changing actions with victim credentials.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"next.js","vendor":"vercel"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Next.js is a React framework for building full-stack web applications. Starting in version 16.0.1 and prior to version 16.1.7, `origin: null` was treated as a \"missing\" origin during Server Action CSRF validation. As a result, requests from opaque contexts (such as sandboxed iframes) could bypass origin verification instead of being validated as cross-origin requests. An attacker could induce a victim browser to submit Server Actions from a sandboxed context, potentially executing state-changing actions with victim credentials (CSRF). This is fixed in version 16.1.7 by treating `'null'` as an explicit origin value and enforcing host/origin checks unless `'null'` is explicitly allowlisted in `experimental.serverActions.allowedOrigins`. If upgrading is not immediately possible, add CSRF tokens for sensitive Server Actions, prefer `SameSite=Strict` on sensitive auth cookies, and/or do not allow `'null'` in `serverActions.allowedOrigins` unless intentionally required and additionally protected.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-04-25","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-25T13:57:54Z","kind":"github_poc","ref":"https://github.com/Nayekah/Next.js-Proof-of-Concept","stars":0,"title":"Some Proof-of-Concept (POCs) for CVE-2025-29927, CVE-2026-27978, and CVE-2026-29057 in Next.js."}],"tier":"poc_unverified"},"has_fix":true,"headline":"Next.js: null origin can bypass Server Actions CSRF checks","id":"CVE-2026-27978","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"vercel:next.js","products":["vercel:next.js"],"type":"csrf","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Next.js: Unbounded postponed resume buffering can lead to DoS","id":"CVE-2026-27979"},"packages":[{"ecosystem":"npm","fixed":["16.1.7"],"introduced":["16.0.1"],"last_affected":[],"package":"next","purl":null,"source":"GHSA-mq59-m269-xvcx"},{"ecosystem":"npm","fixed":["16.1.7"],"introduced":["16.0.1"],"last_affected":[],"package":"next","purl":"pkg:npm/next","source":"GHSA-mq59-m269-xvcx"}],"prev":{"headline":"Next.js: null origin can bypass dev HMR websocket CSRF checks","id":"CVE-2026-27977"},"products":["next.js"],"published":"2026-03-17","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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-18","vendors":["vercel"]},"summary":"Attackers can bypass Server Action CSRF checks using null origins from sandboxed iframes, allowing state-changing actions with victim credentials.","url":"https://insights.sbomify.com/CVE-2026-27978/"}