Next.js Vulnerable to Denial of Service (DoS) with Server Actions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| vercel | next.js | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Trusted Artifact Signer 1.1 | |||
| registry.redhat.io/rhtas/rekor-search-ui-rhel9:sha256:571c48ecb2658ce70199c06dc483ea48a16e032a764a6830388ad845f508d981 | cpe:/a:redhat:trusted_artifact_signer:1.1::el9 | RHSA-2025:3807 | 2025-04-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-0013 | 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. |
Github GHSA |
GHSA-7m27-7ghc-44w9 | Next.js Allows a Denial of Service (DoS) with Server Actions |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.802% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vercel
Vercel next.js |
|
| CPEs | cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Vercel
Vercel next.js |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat trusted Artifact Signer |
|
| CPEs | cpe:/a:redhat:trusted_artifact_signer:1.1::el9 | |
| Vendors & Products |
Redhat
Redhat trusted Artifact Signer |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Next.js Vulnerable to Denial of Service (DoS) with Server Actions | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|