vitejs vite up to 6.2.4 information disclosure

Summaryinfo

A vulnerability identified as problematic has been detected in vitejs vite up to 4.5.11/5.4.16/6.0.13/6.1.3/6.2.4. Affected by this issue is some unknown functionality. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2025-31486. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in vitejs vite up to 4.5.11/5.4.16/6.0.13/6.1.3/6.2.4. This affects some unknown functionality. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

Vite is a frontend tooling framework for javascript. The contents of arbitrary files can be returned to the browser. By adding ?.svg with ?.wasm?init or with sec-fetch-dest: script header, the server.fs.deny 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+. 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 4.5.12, 5.4.17, 6.0.14, 6.1.4, and 6.2.5.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-31486 since 03/28/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 4.5.12, 5.4.17, 6.0.14, 6.1.4 or 6.2.5 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• vitejs

Name

• vite

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 5.4.0
• 5.4.1
• 5.4.2
• 5.4.3
• 5.4.4
• 5.4.5
• 5.4.6
• 5.4.7
• 5.4.8
• 5.4.9
• 5.4.10
• 5.4.11
• 5.4.12
• 5.4.13
• 5.4.14
• 5.4.15
• 5.4.16
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4

Website

• Product: https://github.com/vitejs/vite/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion