Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last KEV listing2d
- Last sighting9mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Dec 5, 2025
- EUVDENISA, European Unionlisted Dec 5, 2025
- VulnCheck KEVcommercial researchlisted Dec 3, 2025
- CIRCLaggregator, mirrors the abovelisted Dec 5, 2025, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2025-5
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2025-5
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2025-5
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2025-5
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
674 public reports collected from VulnCheck and CIRCL, first on Dec 3, 2025. Each links to its original source. We have not verified them.
Description
Meta React Server Components contains a remote code execution vulnerability that could allow unauthenticated remote code execution by exploiting a flaw in how React decodes payloads sent to React Server Function endpoints. Please note CVE-2025-66478 has been rejected, but it is associated with CVE-2025- 55182.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.


