CVE-2025-31125 — Vite Vitejs Improper Access Control Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, github)+10
- EPSS 65.2% (30-day exploitation probability)+15
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Npm Vite: fixed in version 6.2.4 — github.com (GitHub Security Advisories)
- Npm Vite: fixed in version 6.1.3 — github.com (GitHub Security Advisories)
- Npm Vite: fixed in version 6.0.13 — github.com (GitHub Security Advisories)
- Npm Vite: fixed in version 5.4.16 — github.com (GitHub Security Advisories)
- Npm Vite: fixed in version 4.5.11 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Feb 12, 2026 — passed 246 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Vitejs Vite, Npm Vite).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Vitejs | Vite | < 4.5.11≥ 5.0.0 and < 5.4.16≥ 6.0.0 and < 6.0.13≥ 6.1.0 and < 6.1.3≥ 6.2.0 and < 6.2.4 | Vulnerable | NIST National Vulnerability Database |
| Vitejs | Vite | version >= 6.2.0, < 6.2.4version >= 6.1.0, < 6.1.3version >= 6.0.0, < 6.0.13version >= 5.0.0, < 5.4.16version < 4.5.11 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Npm | Vite | ≥ 6.2.0 and < 6.2.4≥ 6.1.0 and < 6.1.3≥ 6.0.0 and < 6.0.13≥ 5.0.0 and < 5.4.16< 4.5.11 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | 1.6 | 3.6 | security-advisories@github.com via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.3 | CVSS 3.1 | Medium | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Vite 任意文件读取漏洞POC ★ 6 Apr 1, 2025
- Vite Development Server's @fs endpoint (CVE-2025-31125) to access sensitive files like /etc/passwd and /etc/hosts via crafted URLs. ★ 0 May 3, 2025
- Vite WASM Import Path Traversal 🛡️ ★ 0 May 7, 2025
- 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, ★ 0 Jul 13, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 15, 2026 · 4 reading(s) · max 65.19%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for anomalous data read/export volumes and access to sensitive records.
- Hunt retroactively in logs from before Jan 22, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · npm/vite
- Affected products added · vitejs/vite
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · vitejs/vite
- CVSS changed · 7.5
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-53571 Vite: `server.fs.deny` bypass on Windows alternate paths Jun 22, 2026
- Medium CVE-2026-53632 NTLMv2 hash disclosure via UNC path handling on Windows Jun 22, 2026
- High CVE-2024-52011 launch-editor vulnerable to command injection via the crafted request on Windows Jun 1, 2026
- High CVE-2026-39363 Vite Affected by Arbitrary File Read via Vite Dev Server WebSocket Apr 7, 2026
- High CVE-2026-39364 Vite has a `server.fs.deny` bypass with queries Apr 7, 2026
- Medium CVE-2026-39365 Vite has a Path Traversal in Optimized Deps `.map` Handling Apr 7, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-31125 is "Vite Vitejs Improper Access Control Vulnerability", rated High. It affects Vite (Vitejs); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.5 describes technical severity. EPSS 65.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.