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.

The Next.js Framework on the remote host is affected by multiple vulnerabilities:

  - A vulnerability exists in the Next.js development server where a null origin can bypass cross-site     protections on the HMR (Hot Module Replacement) websocket endpoint. An attacker with access to     attacker-controlled content reachable from the dev server could potentially connect to the HMR websocket     channel and intercept dev traffic, even when allowedDevOrigins configuration is in place. This     vulnerability only affects development mode. (CVE-2026-27977)

  - A vulnerability exists in Next.js where requests with a null origin can bypass CSRF validation in Server     Actions. Requests from opaque contexts such as sandboxed iframes could bypass origin verification instead     of being validated as cross-origin requests. An attacker could manipulate a victim's browser into executing     state-changing Server Actions from a sandboxed context using victim credentials. (CVE-2026-27978)

  - A denial of service vulnerability exists in Next.js applications with Partial Prerendering enabled. The     system fails to consistently enforce maxPostponedStateSize limits when processing next-resume header     requests in non-minimal deployments, allowing an attacker to send oversized POST payloads with the     next-resume header to trigger unbounded memory buffering and cause excessive memory consumption     potentially leading to service disruption. (CVE-2026-27979)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2026-27978)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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.
    (CVE-2026-27978)

ID	Name	Product	Family	Type	Severity
303199	Next.js Framework 16.0.1 < 16.1.7 Multiple Vulnerabilities	Nessus	Misc.	Local	medium
302959	Linux Distros Unpatched Vulnerability : CVE-2026-27978	Nessus	Misc.	Local	medium
438899	SCA: security update for next (GHSA-mq59-m269-xvcx)	Tenable Cloud Security	SCA Checks	Local	medium
438899	SCA: security update for next (GHSA-mq59-m269-xvcx)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-27978

medium

Tenable Plugins

medium

medium

medium

medium