CVE-2025-31125VulnerabilityPublished 22 Jan 2026

CVE-2025-31125: vitejs vite · Information Exposure

Affects vitejs viteSource CVE Database V5

Exploited in the wild · KEV due 12 Feb 2026 · public detection template (Nuclei) · 65% EPSS : upgrade to 4.5.11 now.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 12 Feb 2026 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 65.7% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.5.11

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 22 Jan 2026
Detectable: evidence found.
nuclei template: Vite Development Server - Path Traversal
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV the same day as disclosure
Observed by OffSeq MirageSeen by Mirage: evidence found.
1 exposed host found; no attack traffic recorded

CVE ID reserved
by GitHub_M
2025-03-2615:04Z, 302 days before disclosure
CVE published
on cve.org
2026-01-2218:50Z, t = 0
In Threat Radar
record ingested
2026-01-2218:50Z, 1 minute after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
2026-01-22, the same day as disclosure
KEV remediation due
US federal deadline
2026-02-12, 21 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), OffSeq Mirage (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vitejs/vite to 4.5.11.

Affected software

Product	Affected	Fixed in
npmvitejs/vite`pkg:npm/vitejs/vite`Other threats	Affected <4.5.11	Fixed in 4.5.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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](https://vitejs.dev/config/server-options.html#server-host)) are affected. ### Details - base64 encoded content of non-allowed files is exposed using `?inline&import` (originally reported as `?import&?inline=1.wasm?init`) - content of non-allowed files is exposed using `?raw?import` `/@fs/` isn't needed to reproduce the issue for files inside the project root. ### PoC Original report (check details above for simplified cases): The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice ``` $ npm create vite@latest $ cd vite-project/ $ npm install $ npm run dev ``` Example full URL `http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init`

Impact

For European organizations, the primary impact is the unauthorized disclosure of sensitive information such as source code, environment variables, or internal configuration files during development. This can lead to intellectual property theft, leakage of secrets (API keys, credentials), and increased risk of subsequent targeted attacks. Since the vulnerability requires the Vite dev server to be exposed externally, organizations using remote development setups or cloud-based development environments are particularly at risk. The confidentiality breach can undermine trust, cause compliance issues with data protection regulations like GDPR, and lead to financial and reputational damage. However, the vulnerability does not allow code execution or integrity modification, limiting the scope to confidentiality impact only. The medium severity reflects the moderate risk, but the ease of exploitation in misconfigured environments makes it a relevant concern for software development teams.

Mitigation

1. Upgrade all Vite instances to the fixed versions: 6.2.4, 6.1.3, 6.0.13, 5.4.16, or 4.5.11 as appropriate. 2. Avoid exposing the Vite development server to external networks unless absolutely necessary. Use localhost-only binding or VPNs for remote access. 3. Implement strict network access controls and firewall rules to restrict access to development servers. 4. Review and audit development environment configurations regularly to detect unintended exposure. 5. Use environment variable management and secrets vaults to avoid embedding sensitive data in files accessible by Vite. 6. Educate developers about secure configuration practices and the risks of exposing dev servers. 7. Monitor network traffic and logs for suspicious access attempts to development servers. 8. Consider containerizing or sandboxing development environments to isolate them from production networks.

Summary

CVE-2025-31125 is a vulnerability in the Vite frontend tooling framework, which is widely used for JavaScript application development. The flaw involves the exposure of sensitive information due to improper handling of file imports when the Vite development server is exposed to the network. Specifically, when the server is started with the --host option or configured with server.host to be accessible externally, attackers can exploit query parameters (?inline&import or ?raw?import) to retrieve contents of files that should not be accessible. This can lead to unauthorized disclosure of sensitive source code, configuration files, or other internal data. The vulnerability affects multiple versions of Vite prior to the patched releases 6.2.4, 6.1.3, 6.0.13, 5.4.16, and 4.5.11. The CVSS 3.1 score is 5.3 (medium), reflecting network attack vector, high complexity, no privileges required, but user interaction needed, and impact limited to confidentiality. No known exploits have been reported in the wild yet. The root cause relates to CWE-200 (Exposure of Sensitive Information) and CWE-284 (Improper Access Control). The vulnerability primarily impacts development environments where the dev server is exposed externally, which is not a default configuration but can occur due to misconfiguration or intentional exposure for remote development. Attackers can leverage this to gain access to sensitive files, potentially aiding further attacks or intellectual property theft.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jan 2026, 10:12 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-200, CWE-284

Technical details

References

Community reviews

Related threats