BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-55183High confidence

Meta react-server-dom-webpack — Deserialization of Untrusted Data

Meta · react-server-dom-webpack

5.3MediumCVSS 3.1
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Mitigation available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 7 Jan 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 64.23% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Meta react-server-dom-webpack and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges9 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmreact-server-dom-parcel>= 19.0.0, < 19.0.219.0.2GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-parcel>= 19.1.0, < 19.1.319.1.3GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-parcel>= 19.2.0, < 19.2.219.2.2GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-turbopack>= 19.0.0, < 19.0.219.0.2GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-turbopack>= 19.1.0, < 19.1.319.1.3GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-turbopack>= 19.2.0, < 19.2.219.2.2GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-webpack>= 19.0.0, < 19.0.219.0.2GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-webpack>= 19.1.0, < 19.1.319.1.3GitHub advisory ↗upstream repository advisory · 11 Dec 2025
npmreact-server-dom-webpack>= 19.2.0, < 19.2.219.2.2GitHub advisory ↗upstream repository advisory · 11 Dec 2025
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-202879

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Mitigation available
01

What, why and how

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.

What

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.

Why

Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Deserialization of Untrusted Data → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-502 ↗

CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-502Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2835Vercel Next.js und React Server Components: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Vercel Next.js und React Server Components ausnutzen, um Informationen offenzulegen und um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV25-834React security advisory (AV25-834)

On December 11, 2025, React Foundation published a security advisory to address vulnerabilities in the following products: Libraries and frameworks bundling react-server implementations are likely to be affected. Common examples include:

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0249Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2025-5222 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=CVE-2025-53547 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55173 https://www.cve.org/CVERecord?id=CVE-2025-55173 Référence CVE CVE-2025-55183 https://www.cve.org/CVERecord?id=CVE-2025-55183 Référence CVE CVE-2025-55184 https://www.cve.org/CVERecord?id=CVE-2025-55184 Référence CVE CVE-2025-57752 https://www.cve.org/CVERecord?id=CVE-2025-57752 Référence CVE CVE-2025-57822 https://www.cve.org/CVERecord?id=CVE-2025-57822 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-58058 https://www.cve.org/CVERecord?id=CVE-2025-58058 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1137Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2025-30698 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-47279 https://www.cve.org/CVERecord?id=CVE-2025-47279 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-54798 https://www.cve.org/CVERecord?id=CVE-2025-54798 Référence CVE CVE-2025-55173 https://www.cve.org/CVERecord?id=CVE-2025-55173 Référence CVE CVE-2025-55182 https://www.cve.org/CVERecord?id=CVE-2025-55182 Référence CVE CVE-2025-55183 https://www.cve.org/CVERecord?id=CVE-2025-55183 Référence CVE CVE-2025-55184 https://www.cve.org/CVERecord?id=CVE-2025-55184 Référence CVE CVE-2025-57752 https://www.cve.org/CVERecord?id=CVE-2025-57752 Référence CVE CVE-2025-57822 https://www.cve.org/CVERecord?id=CVE-2025-57822 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-67779 https://www.cve.org/CVERecord?id=CVE-2025-67779 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2025-9288 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-022009Facebook の React 等複数ベンダの製品における脆弱性

Facebook の React 等複数ベンダの製品には、不特定の脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0394Kwetsbaarheden verholpen in React Server Components

A vulnerability in React Server Components allows crafted HTTP requests to expose source code, necessitating immediate updates for affected versions.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Mitigation available
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
The Cyber Centre encourages users and administrators to review the web link provided and apply the necessary updates.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Dec 2025 · Last source change 7 Jan 2026, 16:26 UTC · CWE-502 · Deserialization of Untrusted Data

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-202879
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Canadian Centre for Cyber Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-55183 · cve.blacktree.nl