How severe is CVE-2025-31125?

CVE-2025-31125 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-31125 being actively exploited?

Yes. CVE-2025-31125 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-01-22, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2025-31125?

CVE-2025-31125 affects Vitejs Vite. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-31125?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2025-31125 have an EU (EUVD) identifier?

Yes. CVE-2025-31125 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8866. It is also flagged as exploited in the EUVD (since 2026-01-22).

When was CVE-2025-31125 published?

CVE-2025-31125 was published on 2025-03-31 and last updated on 2026-06-17.

CVE-2025-31125

CVE-2025-31125 is a medium-severity vulnerability in Vitejs Vite with a CVSS 3.x base score of 5.3. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2026-01-22). The underlying weakness is classified as CWE-200.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
EPSS exploit prediction: 59% (99th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2026-01-22)
EU (EUVD) id: EUVD-2025-8866
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2026-01-22)
Weakness: CWE-200
Affected product: Vitejs Vite
Published: 2025-03-31
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-31125?: 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 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-31125 being actively exploited?: Yes. CVE-2025-31125 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-01-22, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2025-31125?: CVE-2025-31125 affects Vitejs Vite. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-31125?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2025-31125 have an EU (EUVD) identifier?: Yes. CVE-2025-31125 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8866. It is also flagged as exploited in the EUVD (since 2026-01-22).
When was CVE-2025-31125 published?: CVE-2025-31125 was published on 2025-03-31 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:vitejs:vite:*:*:*:*:*:node.js:*:*

More vulnerabilities in Vitejs Vite

CVE-2026-53571 — High (CVSS 7.5): Vite is a frontend tooling framework for JavaScript. Prior to 8.0.16, 7.3.5, and 6.4.3, the contents of files that are…
CVE-2026-39364 — High (CVSS 7.5): Vite is a frontend tooling framework for JavaScript. From 7.1.0 to before 7.3.2 and 8.0.5, on the Vite dev server,…
CVE-2026-39363 — High (CVSS 7.5): Vite is a frontend tooling framework for JavaScript. From 6.0.0 to before 6.4.2, 7.3.2, and 8.0.5, if it is possible to…
CVE-2024-23331 — High (CVSS 7.5): Vite is a frontend tooling framework for javascript. The Vite dev server option `server.fs.deny` can be bypassed on…
CVE-2023-34092 — High (CVSS 7.5): Vite provides frontend tooling. Prior to versions 2.9.16, 3.2.7, 4.0.5, 4.1.5, 4.2.3, and 4.3.9, Vite Server Options…
CVE-2025-24010 — Medium (CVSS 6.5): Vite is a frontend tooling framework for javascript. Vite allowed any websites to send any requests to the development…

All CVEs affecting Vitejs Vite →

Other CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities

CVE-2026-27604 — Critical (CVSS 10.0): FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version…
CVE-2026-40965 — Critical (CVSS 10.0): Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a…
CVE-2026-42826 — Critical (CVSS 10.0): Exposure of sensitive information to an unauthorized actor in Azure DevOps allows an unauthorized attacker to disclose…
CVE-2025-29270 — Critical (CVSS 10.0): Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics devices DSE855 v1.1.0 to v1.1.26 allows…
CVE-2025-61481 — Critical (CVSS 10.0): An issue in MikroTik RouterOS v.7.14.2 and SwOS v.2.18 exposes the WebFig management interface over cleartext HTTP by…
CVE-2025-53624 — Critical (CVSS 10.0): The Docusaurus gists plugin adds a page to your Docusaurus instance, displaying all public gists of a GitHub user.…

Browse all CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities →