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.
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.
- Published
- Dec 11, 2025
- Updated
- Jun 17, 2026
- EPSS
- 64.2% · 99th percentile
- CWE
- CWE-502
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 19 / 30 · 64.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Meta
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- facebook react19.2.0 and later · before 19.2.2
- facebook react19.1.0 and later · before 19.1.3
- facebook react19.0.0 and later · before 19.0.2
- vercel next.js15.3.0 and later · before 15.3.8
- vercel next.js15.4.0 and later · before 15.4.10
- vercel next.js15.5.0 and later · before 15.5.9
- vercel next.js15.0.0 and later · before 15.0.7
- vercel next.js16.0.0 and later · before 16.0.10
- vercel next.js15.1.0 and later · before 15.1.11
- vercel next.js15.2.0 and later · before 15.2.8
- vercel next.js15.6.0
- vercel next.js16.1.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Meta). Independent of NVD's CPE analysis and usually ahead of it.
Meta react-server-dom-parcel
- 19.0.0 and later · up to and including 19.0.1affected · semver
- 19.1.0 and later · up to and including 19.1.2affected · semver
- 19.2.0 and later · up to and including 19.2.1affected · semver
Meta react-server-dom-turbopack
- 19.0.0 and later · up to and including 19.0.1affected · semver
- 19.1.0 and later · up to and including 19.1.2affected · semver
- 19.2.0 and later · up to and including 19.2.1affected · semver
Meta react-server-dom-webpack
- 19.0.0 and later · up to and including 19.0.1affected · semver
- 19.1.0 and later · up to and including 19.1.2affected · semver
- 19.2.0 and later · up to and including 19.2.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | react-server-dom-parcel | from 19.0.0 · before 19.0.2 | 19.0.2 |
| npm | react-server-dom-parcel | from 19.1.0 · before 19.1.3 | 19.1.3 |
| npm | react-server-dom-parcel | from 19.2.0 · before 19.2.2 | 19.2.2 |
| npm | react-server-dom-turbopack | from 19.0.0 · before 19.0.2 | 19.0.2 |
| npm | react-server-dom-turbopack | from 19.1.0 · before 19.1.3 | 19.1.3 |
| npm | react-server-dom-turbopack | from 19.2.0 · before 19.2.2 | 19.2.2 |
| npm | react-server-dom-webpack | from 19.0.0 · before 19.0.2 | 19.0.2 |
| npm | react-server-dom-webpack | from 19.1.0 · before 19.1.3 | 19.1.3 |
| npm | react-server-dom-webpack | from 19.2.0 · before 19.2.2 | 19.2.2 |
Same product
vercel: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-29927Authorization Bypass in Next.js Middleware66This week
- CVE-2024-46982Cache Poisoning in next.js48Plan
- CVE-2021-43803Unexpected server crash in Next.js43Plan
- CVE-2026-75604Next.js: Unauthenticated Remote Code Execution on windows-hosted servers37Monitor
- CVE-2026-44578Next.js: Server-side request forgery in applications using WebSocket upgrades35Monitor
- CVE-2026-64649Next.js: Server-Side Request Forgery in Server Actions on Custom Servers33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:react-server-dom-parcel | 19.0.2 | Package registry (OSV) |
| npm:react-server-dom-parcel | 19.1.3 | Package registry (OSV) |
| npm:react-server-dom-parcel | 19.2.2 | Package registry (OSV) |
| npm:react-server-dom-turbopack | 19.0.2 | Package registry (OSV) |
| npm:react-server-dom-turbopack | 19.1.3 | Package registry (OSV) |
| npm:react-server-dom-turbopack | 19.2.2 | Package registry (OSV) |
| npm:react-server-dom-webpack | 19.0.2 | Package registry (OSV) |
| npm:react-server-dom-webpack | 19.1.3 | Package registry (OSV) |
| npm:react-server-dom-webpack | 19.2.2 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×6
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:2 | 2025-12-11 |
| Proof-of-concept repository on GitHub | stars:7 | 2025-12-12 |
| Proof-of-concept repository on GitHub | stars:8 | 2025-12-12 |
| Proof-of-concept repository on GitHub | stars:4 | 2025-12-12 |
| Proof-of-concept repository on GitHub | stars:0 | 2025-12-12 |
| Proof-of-concept repository on GitHub | stars:5 | 2025-12-12 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-1 d
- Published
- TodaySep 30, 2026+293 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)job = pickle.loads(payload)Fixed
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig): raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.