Known exploited vulnerability

CVE-2025-31125

highCVSS 3.1 7.5In CISA KEVEPSS 75%Published · vitejs

The short answer

CVE-2025-31125 affects vitejs vite and is rated high (CVSS 7.5). CISA added it to the Known Exploited Vulnerabilities catalog on 2026-01-22: attackers are using it, so patch it first. Fixed versions are published for vite (6.2.4, 6.1.3, 6.0.13).

What it is

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.

Weakness: CWE-200, CWE-284.

Severity

7.5 high

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

Exploited (CISA KEV)

Yes, since Jan 22, 2026

Federal due date Feb 12, 2026

EPSS, next 30 days

75%

Higher than 100% of scored CVEs

How it can be exploited

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

What CISA says to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Affected packages and fixed versions

PackageEcosystemFixed inAdvisory
vitenpm6.2.4, 6.1.3, 6.0.13, 5.4.16, 4.5.11GHSA-4r4m-qw57-chr8

Is it in your code? Drop your lockfile into the free vulnerability check, or let vulnerability watch check your repository every day and open the upgrade as a pull request.

Affected products

vite. NVD's record lists the exact affected versions.

References

Questions

Is CVE-2025-31125 being exploited?

Yes. CISA added CVE-2025-31125 to its Known Exploited Vulnerabilities catalog on 2026-01-22, with a federal remediation due date of 2026-02-12.

How do I fix CVE-2025-31125?

Upgrade to a fixed version: vite (npm) 6.2.4 or 6.1.3 or 6.0.13 or 5.4.16 or 4.5.11. CISA's 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.

From NVD, CISA KEV, FIRST EPSS and OSV.dev, checked . Status on NVD: Analyzed. The description is NVD's text, quoted as published.

Related

Know the day a CVE lands in your code

Connect a GitHub repository and ZeusQA checks its dependencies daily, briefs each advisory and opens the fix. Three test runs free, no card.