NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2025-31486 — vite

MEDIUMFix: vitejs/vite@62d7e81

CVE-2025-31486 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in vite. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for vite — see the affected versions and patch details below.

Vite allows server.fs.deny to be bypassed with .svg or relative paths

Also known asGHSA-xcj6-pq6g-qj4x
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-31486.

EPSS Exploitation Probability

via FIRST.org ↗
40.5%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
0.00%17.3%34.6%51.9%2.5%40.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
vitenpm
257.8Mdownloads / week

Description

Summary

The contents of arbitrary files can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.

Details

.svg

Requests ending with .svg are loaded at this line. https://github.com/vitejs/vite/blob/037f801075ec35bb6e52145d659f71a23813c48f/packages/vite/src/node/plugins/asset.ts#L285-L290 By adding ?.svg with ?.wasm?init or with sec-fetch-dest: script header, the restriction was able to bypass.

This bypass is only possible if the file is smaller than build.assetsInlineLimit (default: 4kB) and when using Vite 6.0+.

relative paths

The check was applied before the id normalization. This allowed requests to bypass with relative paths (e.g. ../../).

PoC

npm create vite@latest
cd vite-project/
npm install
npm run dev

send request to read etc/passwd

curl 'http://127.0.0.1:5173/etc/passwd?.svg?.wasm?init'

curl 'http://127.0.0.1:5173/@fs/x/x/x/vite-project/?/../../../../../etc/passwd?import&?raw'

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦npmvite≥ 6.2.0&&< 6.2.56.2.5npm install vite@6.2.5
📦npmvite≥ 6.1.0&&< 6.1.46.1.4npm install vite@6.1.4
📦npmvite≥ 6.0.0&&< 6.0.146.0.14npm install vite@6.0.14
📦npmvite≥ 5.0.0&&< 5.4.175.4.17npm install vite@5.4.17
📦npmviteall versions4.5.12npm install vite@4.5.12
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

iSee857/CVE-2025-31486-PoC

Vite任意文件读取漏洞批量检测脚本CVE-2025-31486

⭐ 6🍴 0May 2025

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update vite to 6.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31486 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How to detect CVE-2025-31486

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2025-31486 -u https://target
Template
Vite server.fs.deny Bypass - Local File Inclusion
Severity
medium
Impact
Attackers can bypass server.fs.deny restrictions to read arbitrary files smaller than 4kB when the Vite dev server is exposed to the network, potentially exposing sensitive configuration data.
Remediation
Update Vite to version 4.5.12, 5.4.17, 6.0.14, 6.1.4, 6.2.5 or later.

Template by ProjectDiscovery nuclei-templates (wn147), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Summary The contents of arbitrary files can be returned to the browser. ### Impact Only apps explicitly exposing the Vite dev server to the network (using --host or [server.host config option](https://vitejs.dev/config/server-options.html#server-host)) are affected. ### Details #### `.svg` Requests ending with `.svg` are loaded at this line. https://github.com/vitejs/vite/blob/037f801075ec35bb6e52145d659f71a23813c48f/packages/vite/src/node/plugins/asset.ts#L285-L290 By adding `?.svg` with `?.wasm?init` or with `sec-fetch-dest: script` header, the restriction was able to bypass. This
O3 Security · Impact-Aware SCA

Is CVE-2025-31486 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-31486: vite — Fixed in 6.2.5