← Übersicht Nicht im beobachteten Stack

Next.js: Unbounded postponed resume buffering can lead to DoS

CVE-2026-27979 · GHSA-h27x-g6w4-24gq

Mittel · CVSS 6.9 Red Hat: Moderate Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
17.03.2026
Zuletzt geändert
25.03.2026
EPSS (30 Tage)
0.8 %
CVSS-Vektor
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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, a request containing the `next-resume: 1` header (corresponding with a PPR resume request) would buffer request bodies without consistently enforcing `maxPostponedStateSize` in certain setups. The previous mitigation protected minimal-mode deployments, but equivalent non-minimal deployments remained vulnerable to the same unbounded postponed resume-body buffering behavior. In applications using the App Router with Partial Prerendering capability enabled (via `experimental.ppr` or `cacheComponents`), an attacker could send oversized `next-resume` POST payloads that were buffered without consistent size enforcement in non-minimal deployments, causing excessive memory usage and potential denial of service. This is fixed in version 16.1.7 by enforcing size limits across all postponed-body buffering paths and erroring when limits are exceeded. If upgrading is not immediately possible, block requests containing the `next-resume` header, as this is never valid to be sent from an untrusted client.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 4 betroffen, 1 nicht betroffen.

Red Hat Enterprise Linux AI (RHEL AI) 3 BetroffenFix ausstehend rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/disk-image-cuda-rhel9
Red Hat Trusted Artifact Signer BetroffenFix ausstehend rhtas/rekor-search-ui-rhel9
streams for Apache Kafka 2 Betroffenwird nicht behoben com.github.streamshub-console
streams for Apache Kafka 3 Betroffenwird nicht behoben com.github.streamshub-console
Nicht betroffen (1)
Red Hat Enterprise Linux 9Nicht betroffenverwundbarer Code nicht enthaltenaspnetcore-runtime-7.0, aspnetcore-targeting-pack-7.0, dotnet-apphost-pack-7.0, dotnet-host, dotnet-hostfxr-7.0, dotnet-runtime-7.0, dotnet-sdk-7.0, dotnet-sdk-7.0-source-built-artifacts, dotnet-targeting-pack-7.0, dotnet-templates-7.0, dotnet7.0, netstandard-targeting-pack-2.1
Weitere betroffene Pakete (38)
CVEvercel/next.jskein Fix bekanntCVE-2026-27979
NVDvercel:next.js16.0.1 → 16.1.7CVE-2026-27979
TuxCare:npm@next/bundle-analyzer16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/bundle-analyzer16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792206291
TuxCare:npm@next/codemod16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/codemod16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792358598
TuxCare:npm@next/eslint-plugin-next16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/eslint-plugin-next16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792196876
TuxCare:npm@next/font16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/mdx16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/mdx16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792364005
TuxCare:npm@next/plugin-storybook16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/plugin-storybook16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792272245
TuxCare:npm@next/polyfill-module16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/polyfill-module16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792293015
TuxCare:npm@next/polyfill-nomodule16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/polyfill-nomodule16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792304740
TuxCare:npm@next/react-refresh-utils16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/react-refresh-utils16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792326308
TuxCare:npm@next/swc-darwin-arm6416.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-darwin-x6416.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-linux-arm64-gnu16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-linux-arm64-gnu16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792367390
TuxCare:npm@next/swc-linux-arm64-musl16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-linux-x64-gnu16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-linux-x64-gnu16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792346469
TuxCare:npm@next/swc-linux-x64-musl16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-win32-arm64-msvc16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/swc-win32-x64-msvc16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/third-parties16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npm@next/third-parties16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792338234
TuxCare:npmcreate-next-app16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npmcreate-next-app16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792195747
TuxCare:npmeslint-config-next16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npmnext16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npmnext-rspack16.0.6-tuxcare.6CLSA-2026-1786710099
TuxCare:npmnext-rspack16.0.6-tuxcare.0 → 16.0.6-tuxcare.6CLSA-2026-1792256965
npmnext16.0.1 → 16.1.7GHSA-h27x-g6w4-24gq

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.