Skip to content
Noroxi
NVD / CVE Program· CNA Meta

CVE-2025-55183: 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.

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 64.2% (FIRST EPSS); higher than 99.2% of all records.
  • 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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: react-server-dom-parcel (npm) 19.0.2, 19.1.3, 19.2.2; react-server-dom-turbopack (npm) 19.0.2, 19.1.3, 19.2.2; react-server-dom-webpack (npm) 19.0.2, 19.1.3, 19.2.2.

Add it to your regular patch cycle. Upgrade to react-server-dom-parcel (npm) 19.0.2, 19.1.3, 19.2.2; react-server-dom-turbopack (npm) 19.0.2, 19.1.3, 19.2.2; react-server-dom-webpack (npm) 19.0.2, 19.1.3, 19.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v3.1—Proof of concept Fix available
Published
Dec 11, 2025
Updated
Oct 7, 2026
EPSS
64.2% · 99th percentile

Report tools

JSON

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-55183

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
vercelnext.js
facebookreact

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.

EcosystemPackageAffected rangeFix
npmreact-server-dom-parcelfrom 19.0.0 · before 19.0.219.0.2
npmreact-server-dom-parcelfrom 19.1.0 · before 19.1.319.1.3
npmreact-server-dom-parcelfrom 19.2.0 · before 19.2.219.2.2
npmreact-server-dom-turbopackfrom 19.0.0 · before 19.0.219.0.2
npmreact-server-dom-turbopackfrom 19.1.0 · before 19.1.319.1.3
npmreact-server-dom-turbopackfrom 19.2.0 · before 19.2.219.2.2
npmreact-server-dom-webpackfrom 19.0.0 · before 19.0.219.0.2
npmreact-server-dom-webpackfrom 19.1.0 · before 19.1.319.1.3
npmreact-server-dom-webpackfrom 19.2.0 · before 19.2.219.2.2

Other highest-scoring records for the same primary product.

  • CVE-2025-29927Authorization Bypass in Next.js Middleware
    66This week
  • CVE-2026-75604Next.js: Unauthenticated Remote Code Execution on windows-hosted servers
    60This week
  • CVE-2024-46982Cache Poisoning in next.js
    48Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-57752Aug 29, 2025 · Next.js Affected by Cache Key Confusion for Image Optimization API Routes
    24Monitor
  • ← EarlierCVE-2025-57822Aug 29, 2025 · Next.js Improper Middleware Redirect Handling Leads to SSRF
    33Monitor
  • Later →CVE-2025-59471Jan 26, 2026 · A denial of service vulnerability exists in self-hosted Next.js applications that have `remotePatterns` configured for the Image Optimizer.
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:react-server-dom-parcel19.0.2Package registry (OSV)
npm:react-server-dom-parcel19.1.3Package registry (OSV)
npm:react-server-dom-parcel19.2.2Package registry (OSV)
npm:react-server-dom-turbopack19.0.2Package registry (OSV)
npm:react-server-dom-turbopack19.1.3Package registry (OSV)
npm:react-server-dom-turbopack19.2.2Package registry (OSV)
npm:react-server-dom-webpack19.0.2Package registry (OSV)
npm:react-server-dom-webpack19.1.3Package registry (OSV)
npm:react-server-dom-webpack19.2.2Package 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.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:22025-12-11
Proof-of-concept repository on GitHubstars:72025-12-12
Proof-of-concept repository on GitHubstars:82025-12-12
Proof-of-concept repository on GitHubstars:42025-12-12
Proof-of-concept repository on GitHubstars:02025-12-12
Proof-of-concept repository on GitHubstars:52025-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.

  1. First PoC-1 d
  2. Published
  3. TodayNov 5, 2026+329 d
EPSS, last 120 days

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.

Finders, 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

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records