CVE-2025-67489: vitejs vite-plugin-react · Code Injection
Affects vitejs vite-plugin-reactSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.5.6 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.5.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade vitejs/vite-plugin-react to 0.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubvitejs/vite-plugin-reactpkg:github/vitejs/vite-plugin-reactOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade vite-plugin-react to version 0.5.6 or later to remediate the vulnerability. Development servers should not be exposed to external networks; avoid using the vite --host option to bind the server to all network interfaces unless strictly necessary and secured. Implement network segmentation and firewall rules to restrict access to development servers to trusted internal IP addresses only. Use VPNs or secure tunnels for remote development access instead of exposing dev servers publicly. Regularly audit development environments for exposed services and monitor network traffic for unusual access patterns. Employ strict access controls and multi-factor authentication for developer machines and environments. Additionally, review and sanitize any dynamic import usage in custom server functions to prevent unsafe code execution. Incorporate security scanning tools into the CI/CD pipeline to detect vulnerable dependencies and enforce timely patching. Finally, educate development teams about the risks of exposing development servers and best practices for secure development.
Description
@vitejs/plugin-rs provides React Server Components (RSC) support for Vite. Versions 0.5.5 and below are vulnerable to arbitrary remote code execution on the development server through unsafe dynamic imports in server function APIs (loadServerAction, decodeReply, decodeAction) when integrated into RSC applications that expose server function endpoints. Attackers with network access to the development server can read/modify files, exfiltrate sensitive data (source code, environment variables, credentials), or pivot to other internal services. While this affects development servers only, the risk increases when using vite --host to expose the server on all network interfaces. This issue is fixed in version 0.5.6.