Skip to content
Fencer Vulns
medium 5.3

CVE-2024-56332 json

Next.js Vulnerable to Denial of Service (DoS) with Server Actions

published 2025-01-03 22 mo ago modified 2026-09-10 59 d ago also EUVD-2025-0013 , GHSA-7m27-7ghc-44w9

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Next.js is a React framework for building full-stack web applications. Starting in version 13.0.0 and prior to versions 13.5.8, 14.2.21, and 15.1.2, Next.js is vulnerable to a Denial of Service (DoS) attack that allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. This vulnerability can also be used as a Denial of Wallet (DoW) attack when deployed in providers billing by response times. (Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.). Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. The issue was resolved in Next.js 13.5.8, 14.2.21, and 15.1.2. We recommend that users upgrade to a safe version. There are no official workarounds.

Patch / fix

  • npm next 13.5.8, 14.2.21, 15.1.2
  • vercel next.js 13.5.8, 14.2.21, 15.1.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-56332 updated cvss 5.3

next.js: Next.js Vulnerable to Denial of Service (DoS) with Server Actions

  • Red Hat Enterprise Linux 7 firefox Red Hat Enterprise Linux 8 firefox, thunderbird Red Hat Enterprise Linux 9 dotnet7.0, dotnet-host, dotnet-sdk-7.0, dotnet-hostfxr-7.0, dotnet-runtime-7.0, dotnet-templates-7.0, +6 more
    affected: no fix planned “Out of support scope”
  • Red Hat streams for Apache Kafka com.github.streamshub-console com.github.streamshub-console
    affected: no fix available
  • Red Hat Trusted Artifact Signer 1.1 rhtas 1.1.2-1744101482
    fixed: vendor fix RHSA-2025:3807
  • Red Hat Enterprise Linux 9 firefox, firefox-x11, thunderbird
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
22 mo ago

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm next
>=13.0.0, <13.5.8
>=14.0.0, <14.2.21
>=15.0.0, <15.1.2
13.5.8
14.2.21
15.1.2

Affected products

  • vercel next.js

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.