dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-67489

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
@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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Arbitrary remote code execution vulnerability in @vitejs/plugin-rs versions 0.5.5 and below allows attackers to execute malicious code through unsafe dynamic imports in server function APIs (loadServerAction, decodeReply, decodeAction) when the development server is exposed to untrusted networks.

MitigationUpgrade @vitejs/plugin-rs to version 0.5.6 or later, and ensure development servers are not exposed to untrusted networks (avoid using vite --host in insecure environments).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of @vitejs/plugin-rs
    Run 'npm list @vitejs/plugin-rs' or inspect package.json dependencies to determine the exact installed version
    Affected if Version is 0.5.5 or lower
  2. Search for usage of vulnerable server function APIs
    Review codebase for imports or calls to loadServerAction, decodeReply, or decodeAction exported by @vitejs/plugin-rs
    Affected if Any of these three APIs (loadServerAction, decodeReply, decodeAction) are being invoked in the application code
  3. Check if development server is network-exposed
    Examine vite.config.js and package.json scripts for the '--host' flag or binding to 0.0.0.0 (e.g., 'vite --host', 'npm run dev -- --host')
    Affected if The dev server is configured to listen on all network interfaces or bound to a public IP address
  4. Verify external network accessibility to dev server
    Review firewall rules, cloud security groups, or network configuration to determine if the dev server port (default 5173) is reachable from untrusted networks or the internet
    Affected if The development server port is accessible from untrusted or unauthorized network segments

Environment is affected if @vitejs/plugin-rs version 0.5.5 or lower is installed, vulnerable APIs are in use, AND the development server is exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade @vitejs/plugin-rs to version 0.5.6 or later, and ensure development servers are not exposed to untrusted networks (avoid using vite --host in insecure environments).

Recommended fix High confidence

@vitejs/plugin-rs version 0.5.6

  1. Update your package.json to specify @vitejs/plugin-rs version 0.5.6 or later
  2. Run npm update @vitejs/plugin-rs or npm install @vitejs/[email protected] to install the fixed version
  3. Verify the installed version matches 0.5.6 or higher using npm list @vitejs/plugin-rs
  4. Restart your Vite development server to load the updated plugin

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67489 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data