dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Feb 2026.
ViteApplication · Vitejs

CVE-2025-31125

HIGH · 7.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 4.5.11 / 5.4.16 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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
Vite is a frontend tooling framework for javascript. Vite exposes content of non-allowed files using ?inline&import or ?raw?import. Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected. This vulnerability is fixed in 6.2.4, 6.1.3, 6.0.13, 5.4.16, and 4.5.11.

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

Vite's dev server has an information disclosure vulnerability where special query parameters (?inline&import or ?raw?import) can be used to read files outside the allowed directory. Only Vite dev servers exposed to the network (via --host or server.host config) are affected.

MitigationUpgrade Vite to version 6.2.4, 6.1.3, 6.0.13, 5.4.16, or 4.5.11 (or later), or ensure the dev server is not exposed to the network by removing --host and server.host configurations.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ViteApplication
Affected:< 4.5.11>= 5.0.0, < 5.4.16>= 6.0.0, < 6.0.13>= 6.1.0, < 6.1.3>= 6.2.0, < 6.2.4

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
None
Availability
None

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

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. Determine installed Vite version
    Run 'npm list vite' in the project directory, check package.json dependencies, or run 'npx vite --version'
    Affected if Version is less than 4.5.11, or between 5.0.0-5.4.15, 6.0.0-6.0.12, 6.1.0-6.1.2, or 6.2.0-6.2.3
  2. Check vite.config for server.host exposure
    Inspect vite.config.js, vite.config.ts, or equivalent for 'server.host' setting set to true or a network IP
    Affected if server.host is set to true, a non-localhost IP, or '0.0.0.0'
  3. Check dev script for --host flag
    Inspect scripts in package.json; look for 'vite --host' or 'vite dev --host' in the dev script
    Affected if The --host flag is present in any dev-related script

If the installed Vite version falls within any of the vulnerable ranges AND the dev server is exposed to the network via server.host or --host flag, the environment is affected by this path traversal vulnerability.

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
Upgrade available Upgrade to 4.5.11 / 5.4.16 / 6.0.13 or later
Fixed in 4.5.115.4.166.0.13
Vendor patch github.com →
Interim mitigation

Upgrade Vite to version 6.2.4, 6.1.3, 6.0.13, 5.4.16, or 4.5.11 (or later), or ensure the dev server is not exposed to the network by removing --host and server.host configurations.

Recommended fix High confidence

Upgrade to 4.5.11, 5.4.16, 6.0.13, 6.1.3, or 6.2.4 depending on your current major version branch

  1. 1. Check current Vite version by running 'npm list vite' or viewing package.json
  2. 2. Identify which major version line you are currently on (4.x, 5.x, or 6.x)
  3. 3. Upgrade to the appropriate fixed version: if on 4.x upgrade to 4.5.11, if on 5.x upgrade to 5.4.16, if on 6.0.x upgrade to 6.0.13, if on 6.1.x upgrade to 6.1.3, if on 6.2.x upgrade to 6.2.4
  4. 4. Run 'npm update vite' or 'npm install vite@<fixed-version>' to apply the upgrade
  5. 5. Rebuild and restart your development server
  6. 6. If your server was exposed to the network using --host or server.host, verify the vulnerability is no longer exploitable using ?inline&import or ?raw?import on sensitive file paths
Caveat Patch releases typically have no breaking changes; review the Vite changelog for any minor notes

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

Fix this in Vite Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31125 — 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-31125 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