Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2025-55183: Source Code Disclosure in React Server Components

Published Dec 11, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS61.9%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
VercelMeta Platforms
IdentifiersCVE-2025-55183CWE-497

CVE-2025-55183 is an information disclosure vulnerability in React Server Components packages react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. Affected versions are 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1. A crafted HTTP request can manipulate Server Function arguments so that string conversion exposes the compiled source code of other Server Functions. Exploitation requires a Server Function that explicitly or implicitly exposes a stringified argument. Dependent frameworks are also affected, including vulnerable Next.js 15.x and 16.x applications using the App Router. The vulnerability has a CVSS score of 5.3 and does not enable remote code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises confidentiality by disclosing compiled Server Function code and application business logic. Secrets can also be disclosed if they are embedded directly in the exposed code, including values inlined by the bundler. The vulnerability does not inherently expose environment variables or secrets stored outside the compiled function code, and does not itself provide remote code execution.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict external access to vulnerable Server Function and App Router endpoints and protect preview and older deployments with deployment access controls. Review Server Functions for explicit or implicit argument stringification and avoid exposing stringified attacker-controlled arguments. Apply current WAF protections for known exploit patterns, but do not treat them as a substitute for upgrading. F5 WAF deployments can enable attack signature 200009348, 'Next.js Server Function Code Exposure,' in blocking mode with updated signatures. No complete workaround replaces patching.

Remediation

Patch, then assume compromise.

Upgrade affected React Server Components packages to 19.0.2, 19.1.3, or 19.2.2 or later in the corresponding release line. These are the initial fixes for this disclosure vulnerability; use the latest supported security release to address subsequent, separate React Server Components vulnerabilities as well. For Next.js, the initial fixed releases are 15.0.6, 15.1.10, 15.2.7, 15.3.7, 15.4.9, 15.5.8, and 16.0.9, with canary fixes in 15.6.0-canary.59 and 16.1.0-canary.17. Rebuild and redeploy affected applications, including accessible older and preview deployments. Remove embedded secrets and rotate any credentials potentially disclosed through compiled Server Function code.

Public exploits

Exploits

7 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2025-55183This repository provides a scanner tool (written in Rust) and a deliberately vulnerable React application for testing CVE-2025-55183, a critical source code disclosure vulnerability in React 19.0.0-19.2.1 Server Actions. The scanner (scanner/src/main.rs) automates the exploitation process by: 1. Fetching the target web page and extracting Server Action IDs. 2. Sending crafted POST requests with a special payload and header to trigger the vulnerability. 3. Receiving and analyzing responses for exposed source code and secrets. 4. Highlighting and saving any detected secrets (API keys, database URLs, credentials, etc.). The vulnerable-app directory contains a Next.js application with multiple server actions, each hardcoding various secrets, API keys, and credentials for demonstration purposes. These include Stripe, AWS, SendGrid, Twilio, Firebase, Google, GitHub, DataDog, Sentry, Slack, Discord, and multiple database and message queue connection strings. The scanner is operational and can be used to test real-world targets for this vulnerability. It is not a detection script but a full exploit that can extract sensitive information if the target is vulnerable. The attack vector is network-based, targeting web applications running the affected React versions. Numerous fingerprintable endpoints and secrets are present in the demo app, making it suitable for both research and red team exercises.Saturate · Disclosed Dec 11, 2025 · rust · typescript · networkOperationalCVE-2025-55183_POCThis repository contains a Python exploit (exp.py) and a README for CVE-2025-55183, a source code disclosure vulnerability in Next.js React Server Components (RSC). The exploit works in three main steps: (1) it discovers JavaScript chunk files from a given Next.js page, (2) extracts server action IDs from those chunks, and (3) sends crafted HTTP POST requests with a special payload to the server, attempting to trigger the vulnerability and leak the source code of server functions. The exploit is operational and can save or print the leaked source code. The only code file is exp.py, which is a standalone script using the requests library. The attack vector is network-based, requiring HTTP(S) access to the target. The script supports optional proxying and output to a file. No hardcoded credentials or static IPs are present, but the script interacts with endpoints such as /_next/static/chunks/ and the root path with a custom header. The README provides usage instructions and context. The exploit is not a detection script; it actively attempts to extract source code from vulnerable targets.X-Cotang · Disclosed Dec 12, 2025 · python · markdown · networkOperationalreact-server-cve-labThis repository is a comprehensive security lab for demonstrating and testing two critical vulnerabilities in React Server Components: CVE-2025-55183 (Source Code Exposure) and CVE-2025-55184 (Denial of Service). The structure includes: - A deliberately vulnerable Next.js application (vulnerable-app/) running React 19.0.0 and Next.js 15.0.2, with server actions containing hardcoded secrets and business logic in 'app/actions.js'. - Two operational Python exploit scripts: 'exploits/exploit-55183.py' (extracts server-side source code and secrets via a crafted POST request) and 'exploits/exploit-55184.py' (sends a payload to hang the server, causing a DoS). - A scanner tool (scanner/scan.py) for automated detection of both CVEs. - Extensive documentation (DOCUMENTATION.md, README.md) detailing the vulnerabilities, exploitation techniques, detection, and remediation. The main exploit capabilities are: - For CVE-2025-55183: Unauthenticated attackers can extract server-side source code, including secrets, by sending a crafted HTTP POST request to the vulnerable endpoint. The exploit script automates this process and saves the leaked code to a file. - For CVE-2025-55184: Attackers can send a specially crafted payload to cause infinite promise recursion, hanging the Node.js server and requiring a manual restart. The repository is intended for educational and research purposes, providing both the vulnerable application and the tools to exploit and detect these vulnerabilities. The attack vector is network-based, requiring only HTTP access to the target. The endpoints targeted are typically the root or main HTTP endpoint of the vulnerable application (e.g., http://localhost:3000).StealthMoud · Disclosed Dec 12, 2025 · python · javascript · networkOperationalReact2P4IM0NshellThis repository is a Chrome extension named 'React2P4IM0Nshell' designed for advanced security auditing and exploitation of Next.js and React Server Components (RSC) environments. The extension provides a browser-based interface to scan, fingerprint, and exploit three specific vulnerabilities (CVE-2025-55182: RCE, CVE-2025-55183: Source Leak, CVE-2025-55184: DoS). The main exploit logic resides in 'content.js', which injects scripts into web pages to perform passive and active reconnaissance, and to execute exploit payloads via crafted HTTP requests. The RCE module sends a multipart/form-data POST request to a derived endpoint (e.g., '/adfa') with a JSON payload that triggers backend command execution. The source leak module fetches Next.js chunk files to extract sensitive Action IDs and potentially leak server-side code. The DoS module abuses promise references to cause infinite loops on the server. The extension also includes a UI (popup.html, popup.js) for user interaction, payload generation (reverse shells for Linux/Windows), and an embedded Alpine Linux terminal via an iframe. The extension is intended for ethical research and lab use, as emphasized in the README. No hardcoded external IPs or domains are present, but the extension targets endpoints on the currently loaded web page, making it adaptable to any site the user visits. The codebase is primarily JavaScript, with supporting HTML, CSS, and JSON files.MammaniNelsonD · Disclosed Dec 14, 2025 · javascript · json · browser · networkOperationalCVE-2025-55182This repository is a Next.js 15.0.0 research/PoC web application ("NextCorp") that demonstrates three security scenarios attributed to Next.js/React Server Components/Flight protocol handling. It is not a standalone exploit tool; instead it is a vulnerable target + demonstration harness implemented as a web app. Key exploit capabilities implemented in code: - RCE demo (claimed CVE-2025-55182): app/vulnerabilities/rce/submit/route.ts parses JSON and, if it detects '__proto__', 'child_process', or a 'rce_cmd' field, executes an OS command via Node's child_process.exec and returns stdout/stderr in the HTTP response. The client page app/vulnerabilities/rce/page.tsx sends a baseline POST to /vulnerabilities/rce/submit intended for interception and modification (e.g., adding rce_cmd). - Information disclosure demo (claimed CVE-2025-55183): app/actions.ts defines a server action importantBusinessLogic that checks for the marker string "${jndi:source_leak}" in form input and then performs an actual local file read (fs.readFileSync) of app/actions.ts (path built from process.cwd()). The content is returned to the user, simulating a server action source leak. - DoS demo (claimed CVE-2025-55184): app/vulnerabilities/dos/submit/route.ts checks incoming JSON for the substring '$L1' and then runs a busy-wait loop to simulate CPU exhaustion/hang, with a 10-second failsafe to avoid permanent lockup. Repository structure/purpose: - UI pages under app/ provide a SaaS-like front-end with navigation (app/page.tsx, app/components/Header.tsx) and three vulnerability modules under app/vulnerabilities/{rce,info-disclosure,dos}/page.tsx. - Two App Router route handlers implement the server-side vulnerable behaviors: app/vulnerabilities/rce/submit/route.ts and app/vulnerabilities/dos/submit/route.ts. - A server action in app/actions.ts implements the source-leak behavior and contains hardcoded "secret" strings to illustrate sensitive data exposure. - Documentation (README.md, TESTING.md) explains reproduction steps and provides example payloads and curl commands. Overall, the code provides operational, locally testable exploit effects (real command execution, real file read, and real CPU busy-loop) triggered via HTTP requests to specific Next.js endpoints.dbwlsdnr95 · Disclosed Dec 20, 2025 · Framework: Next.js (custom PoC app using Next.js App Router + Route Handlers) · typescript · tsx · networkOperationalCVE-2025-55182This repository is a real exploit project centered on exploit/react2shell.py, a standalone Python exploit for CVE-2025-55182 affecting React Server Components in vulnerable React/Next.js deployments. The repository also includes extensive markdown analysis, a deliberately vulnerable Next.js lab application, an auxiliary curl-based exploit script, and a restoration script for resetting the lab after destructive testing. The main exploit is not merely a detector: it builds a malicious multipart/form-data request that targets Next.js Server Action / React Flight deserialization. The payload abuses prototype pollution ("$1:__proto__:then") and constructor traversal ("$1:constructor:constructor") to reach the JavaScript Function constructor, then executes attacker-controlled JavaScript in the Node.js process. That JavaScript invokes child_process.execSync() to run arbitrary shell commands. Command output is exfiltrated by throwing a NEXT_REDIRECT error whose digest is converted by Next.js into the X-Action-Redirect response header, typically embedding output in a /login?a=... redirect value. Capabilities described and partially visible in the code/docs include: vulnerability checking with a benign echo command, arbitrary command execution, interactive shell mode, environment-variable theft using a temp file and line-by-line reads to bypass header-size limits, website defacement, deletion of project/dashboard content, and server shutdown/DoS actions. This makes the exploit operational rather than a simple PoC. Repository structure: - exploit/react2shell.py: primary exploit implementation in Python using requests and argparse. - exploit/exploit-explanation.md: usage and architecture documentation. - docs/analysis/*.md: root-cause analysis, payload anatomy, and disclosure timeline. - vulnerable-app/: intentionally vulnerable Next.js 15.0.0 + React 19.0.0 demo target. - vulnerable-app/curl_id.sh: bash/curl variant of the exploit. - vulnerable-app/scripts/restore.sh: lab restoration helper. Fingerprintable observables include the target root path /, local demo URL http://localhost:3000, required headers Next-Action / X-Nextjs-Request-Id / X-Nextjs-Html-Request-Id, response header X-Action-Redirect, exfiltration redirect path /login?a=${res}, and temp file /tmp/stolen_env.txt. The vulnerable app itself exposes a server action in vulnerable-app/app/actions.ts and a client page in app/page.tsx, but the vulnerability is in the underlying React/Next.js deserialization path rather than in custom application logic.devianntsec · Disclosed Mar 25, 2026 · python · typescript · web · networkOperationalCVE-2025-55182-React2Shell-Nextjs-RSC-AnalysisThis repository is a research-oriented Proof of Concept (PoC) environment demonstrating three critical vulnerabilities in Next.js 15.0.0 (with React 19.0.0 Server Components): Remote Code Execution (CVE-2025-55182), Information Disclosure (CVE-2025-55183), and Denial of Service (CVE-2025-55184). The structure is a simulated SaaS application ('NextCorp') with dedicated pages and endpoints for each vulnerability under /app/vulnerabilities/. - The RCE exploit is triggered by sending a specially crafted JSON payload (containing a __proto__ object with a script) to /vulnerabilities/rce/submit, simulating arbitrary command execution on the server. - The Info Disclosure exploit targets /vulnerabilities/info-disclosure, where manipulating the Next-Action header or request body can cause the server to leak sensitive server-side source code (such as the importantBusinessLogic function containing secrets). - The DoS exploit is demonstrated by sending a recursive/circular JSON payload to /vulnerabilities/dos/submit, causing the server to enter a busy loop and hang (with a failsafe in PoC). The repository is implemented in TypeScript using Next.js and React, with clear separation of vulnerable endpoints and demonstration logic. The PoC is not weaponized but provides a realistic simulation of exploitation scenarios for research and educational purposes.dbwlsdnr95 · Disclosed Dec 20, 2025 · typescript · javascript · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Meta PlatformsReactapplication
VercelNext.Jsapplication
FAQ

Frequently asked questions

Is CVE-2025-55183 exploited in the wild?
As of Oct 19, 2026, Mallory has no reports of CVE-2025-55183 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-55183?
Yes. Mallory tracks 7 public exploits or proofs of concept for CVE-2025-55183, the earliest disclosed Dec 11, 2025.
Is there a patch for CVE-2025-55183?
Upgrade affected React Server Components packages to 19.0.2, 19.1.3, or 19.2.2 or later in the corresponding release line. These are the initial fixes for this disclosure vulnerability; use the latest supported security release to address subsequent, separate React Server Components vulnerabilities as well.
What products are affected by CVE-2025-55183?
Vercel Next.Js and Meta Platforms React.
How severe is CVE-2025-55183?
CVE-2025-55183 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 61.9% (99th percentile) as of Oct 19, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity41Community discussion across Reddit, Mastodon, and other social sources.