# CVE-2025-55183: Source Code Exposure Vulnerability in React Server Components > Attackers can leak source code of Server Functions via crafted HTTP requests if specific argument exposure conditions are met in React Server Components. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Dec 2025 - **Updated:** 7 Jan 2026 - **Also known as:** GHSA-925w-6v3x-g4j4 ## What is CVE-2025-55183? CVE-2025-55183 is a medium-severity vulnerability in Vercel Next.js, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description An information leak vulnerability exists in specific configurations of React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. A specifically crafted HTTP request sent to a vulnerable Server Function may unsafely return the source code of any Server Function. Exploitation requires the existence of a Server Function which explicitly or implicitly exposes a stringified argument. ## Which versions are affected by CVE-2025-55183? 18 open source packages ship an affected version, including react-server-dom-parcel, react-server-dom-turbopack and react-server-dom-webpack. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `react-server-dom-parcel` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-parcel` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-parcel` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-parcel` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-parcel` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-parcel` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-turbopack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-turbopack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-turbopack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-turbopack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-turbopack` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-turbopack` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-webpack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-webpack` | npm | From 19.0.0 | 19.0.2 | | `react-server-dom-webpack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-webpack` | npm | From 19.1.0 | 19.1.3 | | `react-server-dom-webpack` | npm | From 19.2.0 | 19.2.2 | | `react-server-dom-webpack` | npm | From 19.2.0 | 19.2.2 | Products: Facebook React, Vercel Next.js. ## How do I fix CVE-2025-55183? Upgrade react-server-dom-parcel to a fixed version for your release line: 19.0.2, 19.1.3 or 19.2.2. ## Is CVE-2025-55183 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55183 exists. Public exploit code: - Batch upgrade all your Next.js apps to patched versions - fight back against CVE-2025-55183/55184/67779 (github_poc): https://github.com/williavs/nextjs-security-update - PoC for CVE-2025-55183 (github_poc): https://github.com/kimtruth/CVE-2025-55183-poc - Security research lab for CVE-2025-55183 and CVE-2025-55184 in React Server Components (github_poc): https://github.com/StealthMoud/react-server-cve-lab - CVE-2025-55183 POC (github_poc): https://github.com/X-Cotang/CVE-2025-55183_POC - A CVE-2025-55183 secret miner (github_poc): https://github.com/Saturate/CVE-2025-55183 - CVE-2025-55183 Scanner (github_poc): https://github.com/omaidnebari/RSC-Scanner-POC ## Other vulnerabilities in Vercel Next.js - [CVE-2025-55182](https://insights.sbomify.com/CVE-2025-55182/): Meta React Server Components Remote Code Execution (critical 10.0, exploited in the wild) - [CVE-2026-23864](https://insights.sbomify.com/CVE-2026-23864/): React Server Components have multiple Denial of Service Vulnerabilities (high 7.5) - [CVE-2025-55184](https://insights.sbomify.com/CVE-2025-55184/): Denial of Service Vulnerability in React Server Components (high 7.5) - [CVE-2025-67779](https://insights.sbomify.com/CVE-2025-67779/): Denial of Service Vulnerability in React Server Components (high 7.5) - [CVE-2018-6341](https://insights.sbomify.com/CVE-2018-6341/): Cross-Site Scripting in react-dom (medium 6.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-55183 and fix it if it is affected. What it is: CVE-2025-55183 is a medium-severity vulnerability in Vercel Next.js, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55183 exists. Affected packages and fixed versions: - react-server-dom-parcel (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-parcel (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-parcel (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-parcel (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-parcel (npm): affected from 19.2.0; fixed in 19.2.2 - react-server-dom-parcel (npm): affected from 19.2.0; fixed in 19.2.2 - react-server-dom-turbopack (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-turbopack (npm): affected from 19.0.0; fixed in 19.0.2 - react-server-dom-turbopack (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-turbopack (npm): affected from 19.1.0; fixed in 19.1.3 - react-server-dom-turbopack (npm): affected from 19.2.0; fixed in 19.2.2 - react-server-dom-turbopack (npm): affected from 19.2.0; fixed in 19.2.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-55183/ (Markdown: https://insights.sbomify.com/CVE-2025-55183/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55183 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55183 - OSV: https://osv.dev/vulnerability/CVE-2025-55183 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-55183/ Summaries are generated and may contain mistakes; the official description above is the record.