MEDIUM CVSS 5.9
Published: 2026-01-26

CVE-2025-59472

vercel next.js Security Advisory (CVE-2025-59472)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2025-59472?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2025-59472 impacting vercel next.js. Evaluated with CVSS Base Score of 5.9 (MEDIUM).

Original NVD Description

Source: NIST NVD
A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the `Next-Resume: 1` header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion: 1. **Unbounded request body buffering**: The server buffers the entire POST request body into memory using `Buffer.concat()` without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory. 2. **Unbounded decompression (zipbomb)**: The resume data cache is decompressed using `inflateSync()` without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion. Both attack vectors result in a fatal V8 out-of-memory error (`FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server. To be affected you must have an application running with `experimental.ppr: true` or `cacheComponents: true` configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable. Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
High (AC:H)
Depends on race conditions or environment
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
None (C:N)
No data confidentiality impact
Integrity
None (I:N)
No system modification impact
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product vercel / next.js
Affected Versions *
Weakness Enumeration CWE-400

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2025-59472 impacting vercel next.js.

⚡ Nuclei Detection Template (YAML) cve-2025-59472.yaml
id: cve-2025-59472

info:
  name: vercel next.js - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: medium
  description: |
    Automated signature & scanner for CVE-2025-59472 affecting vercel next.js.
    Evaluation: A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endp...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2025-59472
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
    cvss-score: 5.9
    cve-id: CVE-2025-59472
    cwe-id: CWE-400
  tags: cve,cve-2025-59472,vercel,next.js,medium

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "next.js"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2025-59472.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2025-59472
# Target: vercel next.js | CVSS: 5.9 (MEDIUM)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2025-59472 (vercel next.js)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against vercel next.js scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2025-59472.sh
# Recommended Remediation & Patching Commands for CVE-2025-59472
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install next.js 2>/dev/null || \
sudo dnf upgrade next.js 2>/dev/null || \
sudo yum update next.js

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i next.js 2>/dev/null || rpm -qa | grep -i next.js

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2025-59472 in vercel next.js?

Review vendor-specific security notices and update vercel next.js packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2025-59472?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2025-59472?

CVE-2025-59472 is classified with a CVSS 3.1 Base Score of 5.9 (MEDIUM). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
5.9
MEDIUM SEVERITY
CVE ID CVE-2025-59472
Weakness CWE-400
Vendor vercel
Product next.js
Published 2026-01-26
Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H