CVE-2025-31125
CVE-2025-31125 is a medium-severity vulnerability (CVSS 3.1 base score 5.3). Vite Vitejs contains an improper access control vulnerability that exposes content of non-allowed files using ?inline&import or ?raw?import. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-01-22, with a remediation due date of 2026-02-12 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 74.9% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
Vite Vitejs Improper Access Control Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: https://github.com/vitejs/vite/commit/59673137c45ac2bcfad1170d954347c1a17ab949 ; https://nvd.nist.gov/vuln/detail/CVE-2025-31125
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2025-31125 to the KEV catalog 297 days after its CVE record was published. The median for entries added in 2026 so far is 12.5 days.
- Its current EPSS score (74.9%) is higher than that of 59% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2026-01-23).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| vitejs | vitejs vite | >= 6.2.0, < 6.2.4 >= 6.1.0, < 6.1.3 >= 6.0.0, < 6.0.13 >= 5.0.0, < 5.4.16 < 4.5.11 |
References
2 linksRecord Details
- Published
- 2025-03-31
- Last updated
- 2026-01-23
- Assigner (CNA)
- GitHub_M
- Credited to
- -
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.