Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2025-66478-Exploit-PoC — Proof-of-concept exploit demo for CVE-2025-66478 using Node.js | Kitploit
Tools/GitHubGitHub/zhixiangyao/cve-2025-66478-exploit-poc
Dynamic Analysis (Sandboxing)Vulnerability AnalysisCode AnalysisExploitationWeb Application ExploitationLearning & EducationPayload Development
GitHub
Share
zhixiangyao/cve-2025-66478-exploit-poc

CVE-2025-66478-Exploit-PoC

Proof-of-concept exploit demo for CVE-2025-66478 using Node.js

View Repository
15411 months agoNot yet reviewed

CVE-2025-66478 Exploit PoC

This repository contains proof-of-concept (PoC) code for reproducing and researching the Next.js CVE-2025-66478 vulnerability. It includes a vulnerable Next.js application and a Node.js exploit script for testing the vulnerability.

English · 中文

What is CVE-2025-66478?

This is a Remote Code Execution (RCE) vulnerability that occurs during Next.js Server Actions processing.

Key Points:

  • Root Cause: Insecure deserialization in the RSC (React Server Components) Flight protocol.
  • Attack Vector: Prototype pollution via the __proto__ property.

Vulnerability Summary

ItemDescription
CVE IDCVE-2025-66478
TypeRemote Code Execution (RCE)
Root CauseInsecure deserialization in RSC Flight protocol
Severity (CVSS)10.0 (Critical)
ImpactArbitrary system command execution on the server

Attack Mechanism (Technical Details)

  1. Payload Delivery: The attacker crafts a payload using the React Flight serialization format, injecting properties like __proto__.
  2. Insecure Deserialization & Pollution: The server deserializes the payload without proper validation, resulting in Object.prototype being polluted.
  3. Thenable Exploitation Chain: The pollution injects a then property into all objects. Next.js logic incorrectly identifies these objects as Promises (Thenables).
  4. RCE Execution: When the server attempts to await this "fake Promise", the malicious JavaScript code injected into the then method is executed (e.g., child_process.execSync).
sequenceDiagram
    participant Attacker as Attacker
    participant Server as Next.js Server

    Attacker->>Server: POST / (JSON with "__proto__": {"then": ...})
    Note right of Server: JSON parsing pollutes Object.prototype

    Server->>Server: Application logic encounters an object

    rect rgb(200, 150, 150)
    Note right of Server: "Thenable" check exploitation chain
    Server->>Server: Check: typeof obj.then === 'function'?
    Server-->>Server: Yes (due to pollution)
    end

    Server->>Server: Await/execute malicious .then()
    Note right of Server: Malicious JS code runs (RCE)

    Server-->>Attacker: Response (Action redirect / Error message)

Therefore, when the server processes this manipulated Promise, it executes the JavaScript code injected by the attacker, which can lead to system command execution. The included main.mjs is example code for reproducing this attack scenario.

Affected Versions

This vulnerability affects Next.js applications using the App Router.

  • Affected Versions:
    • Next.js 15.x
    • Next.js 16.x
    • Next.js 14.3.0-canary.77 and later (Canary releases)
  • Unaffected Versions:
    • Next.js 13.x
    • Next.js 14.x stable versions
    • Applications using only Pages Router
    • Edge Runtime

Patched Versions:

  • 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7
  • 16.0.7
  • 15.6.0-canary.58 (for PPR users)

References

  • Next.js Security Advisories
  • NVD - CVE-2025-66478
  • Python - CVE-2025-66478
  • CVE-2025-55182

File Structure

  • app/page.tsx: Sample code for the vulnerable application.
  • exploit.mjs: Exploit execution script written in Node.js.

Prerequisites

  • Node.js: v24 or later recommended.

1. Running the Next.js Application

# You can also use yarn or npm.
pnpm install
pnpm dev

Verify that you can access http://localhost:3000 via your browser.

2. Running the Exploit Script

pnpm exploit

By default, it targets the local address (http://localhost:3000). To test a different address, use the --url option:

pnpm exploit --url http://target-ip:3000

Disclaimer

This code is intended for security research and educational purposes only. Using this tool against systems or networks without prior permission is illegal, and users bear full responsibility for any issues arising from such use.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    989
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    576
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    354
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    339
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    323
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    315

Explore all tools

Browse our collection of tools

View all tools →