CVE-2025-67489Public exploitNetwork attack vector

Remote code execution via unvalidated dynamic imports

Published Dec 9, 2025 · Updated Dec 10, 2025

Code injection in @vitejs/plugin-rsc 0.5.5 and earlier allows remote attackers to execute JavaScript through RSC server function requests. The development implementations of loadServerAction, decodeReply, and decodeAction pass attacker-controlled reference IDs to an unrestricted dynamic import, accepting data URL modules instead of limiting IDs to registered references. An RSC application must expose a server-function endpoint on a network-reachable Vite development server; successful execution runs with Node.js privileges and can read or modify files and reach internal services.

CVSS severity9.8
Critical
EPSS probability0.81%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code injection in @vitejs/plugin-rsc 0.5.5 and earlier allows remote attackers to execute JavaScript through RSC server function requests. The development implementations of loadServerAction, decodeReply, and decodeAction pass attacker-controlled reference IDs to an unrestricted dynamic import, accepting data URL modules instead of limiting IDs to registered references. An RSC application must expose a server-function endpoint on a network-reachable Vite development server; successful execution runs with Node.js privileges and can read or modify files and reach internal services.

The record

CVE
CVE-2025-67489
Published
Dec 9, 2025
Updated
Dec 10, 2025
Vendor
ViteJS
Product
@vitejs/plugin-react
Classifications
CWE-94, T1059.007, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 9, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 10, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 0.5.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

ViteJS · @vitejs/plugin-reactversion=< 0.5.6

Published CVSS scores

9.8GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
T1059.007JavaScript/JScript
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo