GHSA-VVGP-WW4W-46VF

Vulnerability from github – Published: 2026-11-19 22:18 – Updated: 2026-11-19 22:18
VLAI
Summary
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
Details

Self-hosted Next.js applications served with next start and built with cacheComponents: true but without Partial Prefetching accept a request-supplied route param value as a prerender placeholder. One unauthenticated GET request can poison the fallback shell cache entry that a family of routes shares.

Such a route is served from a shell that keeps its never-prerenderable params as placeholders, so every value of those params shares one cache entry. A path segment equal to the percent-encoded, bracketed name of its own route param is treated as an unresolved placeholder, and only that param is deferred. A layout above it then renders its concrete value into the shell during the blocking render, and the result, including its HTTP status, is stored under the shared key.

Depending on the application, the stored entry is one of the following:

  • A persistent 404, when the layout rejects the value with notFound(): served to every URL under the shell key with "revalidate": false, across server restarts, with no error logged.
  • A substituted param value, when the layout renders the value: the server-rendered HTML renders the attacker's value for that param in place of the visitor's own. A JavaScript client corrects it on hydration. No markup or script injection is possible, and no data is disclosed.

Preconditions

  1. cacheComponents: true with partialPrefetching unset or false.
  2. Self-hosted serving with next start.
  3. A dynamic route with a prerenderable param (generateStaticParams) whose requested value was not generated at build time.
  4. At least two never-prerenderable params below it: a layout reading the shallower one inside a Suspense boundary, and a deeper one the request supplies as the placeholder.
  5. A blocking fallback shell.

Workarounds

Set partialPrefetching: true in next.config. Otherwise, apps should upgrade to the patched version as soon as possible.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 16.4.4"
      },
      "package": {
        "ecosystem": "npm",
        "name": "next"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "16.4.0"
            },
            {
              "fixed": "16.4.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-119350"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-349"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-19T22:18:08Z",
    "nvd_published_at": "2026-11-16T19:17:27Z",
    "severity": "MODERATE"
  },
  "details": "Self-hosted Next.js applications served with `next start` and built with `cacheComponents: true` but without Partial Prefetching accept a request-supplied route param value as a prerender placeholder. One unauthenticated GET request can poison the fallback shell cache entry that a family of routes shares.\n\nSuch a route is served from a shell that keeps its never-prerenderable params as placeholders, so every value of those params shares one cache entry. A path segment equal to the percent-encoded, bracketed name of its own route param is treated as an unresolved placeholder, and only that param is deferred. A layout above it then renders its concrete value into the shell during the blocking render, and the result, including its HTTP status, is stored under the shared key.\n\nDepending on the application, the stored entry is one of the following:\n\n- A persistent 404, when the layout rejects the value with `notFound()`: served to every URL under the shell key with `\"revalidate\": false`, across server restarts, with no error logged.\n- A substituted param value, when the layout renders the value: the server-rendered HTML renders the attacker\u0027s value for that param in place of the visitor\u0027s own. A JavaScript client corrects it on hydration. No markup or script injection is possible, and no data is disclosed.\n\n### Preconditions\n\n1. `cacheComponents: true` with `partialPrefetching` unset or `false`.\n2. Self-hosted serving with `next start`.\n3. A dynamic route with a prerenderable param (`generateStaticParams`) whose requested value was not generated at build time.\n4. At least two never-prerenderable params below it: a layout reading the shallower one inside a Suspense boundary, and a deeper one the request supplies as the placeholder.\n5. A blocking fallback shell.\n\n### Workarounds\n\nSet `partialPrefetching: true` in `next.config`. Otherwise, apps should upgrade to the patched version as soon as possible.",
  "id": "GHSA-vvgp-ww4w-46vf",
  "modified": "2026-11-19T22:18:08Z",
  "published": "2026-11-19T22:18:08Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/vercel/next.js/security/advisories/GHSA-vvgp-ww4w-46vf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119350"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vercel/next.js/commit/18eeffb5fabd91911852d44cf56948b3f2cbee04"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/vercel/next.js"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vercel/next.js/releases/tag/v16.4.5"
    },
    {
      "type": "WEB",
      "url": "https://nextjs.org/blog/november-2026-security-release"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…