Threats / Meta / CVE-2025-55182
CVE-2025-55182
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Meta React Server Components vulnerability
Meta React Server Components contains an unauthenticated remote code execution vulnerability in payload decoding for React Server Function endpoints. The flaw is actively exploited in the wild and associated with ransomware campaigns.
Verdict
Today item, not a backlog item.
Unauthenticated attackers can execute arbitrary code on affected React Server Components instances by sending malicious payloads to React Server Function endpoints. Active exploitation and ransomware deployment pose immediate risk to production environments.
CISA KEV Yes · 2025-12-055Ransomware use Flagged5EPSS 0.99616 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
593 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-05), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99616 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Meta, React Server Components. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Craft and send a malicious payload to a React Server Function endpoint, exploiting the decoding flaw to achieve code execution without authentication.
Business
Attacker gains full system compromise, enabling data theft, service disruption, and deployment of ransomware to encrypt critical business assets.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Execute commands within the compromised application context to establish persistence, escalate privileges, and move laterally across the infrastructure.
Business
Extended dwell time increases exposure window, allowing attackers to exfiltrate sensitive data and encrypt backups before demanding ransom.
3
Lateral reach — past segmentation narrative 3
Attacker
Deploy ransomware payloads across connected systems and encrypt business-critical data to maximize financial leverage.
Business
Operations halt, revenue stops, and organization faces extortion demands while reputational damage and regulatory penalties accumulate.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05