CVE-2025-31125
Vite Vitejs Improper Access Control Vulnerability
Vite Vitejs
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 22 January 2026. US federal agencies were required to remediate it by 12 February 2026.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 74.9%, which is higher than 99.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2025-31125 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-31125.
What does CVE-2025-31125 affect?
CVE-2025-31125 affects Vite Vitejs. 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.
How severe is CVE-2025-31125?
CVE-2025-31125 is rated MEDIUM with a CVSS base score of 5.3. EPSS puts the probability of exploitation in the next 30 days at 74.9%, higher than 99.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 12 February 2026.
How should organisations respond to CVE-2025-31125?
Apply the vendor patch for Vite Vitejs as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.