Skip to content
vulnerability

CVE-2025-31125

5.3
Medium
KEV · Exploited in wildEPSS 75%Patch available

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.

exploited
Yes, in CISA KEV since 22 Jan 2026fix by 12 Feb 2026 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 74.9%
Published 31 Mar 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

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

triage
server-sideruntimeWAF can block: partlyAV · networkCWE-200· Information ExposureCWE-284· Common Weakness

Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode · response filtering

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexityhighprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialityhighintegritynoneavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
common questions

Is CVE-2025-31125 being exploited?

Yes. CVE-2025-31125 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-31125?

CVE-2025-31125 is rated Medium with a CVSS score of 5.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-31125?

Yes. A fix has been recorded for CVE-2025-31125. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-31125 affect?

CVE-2025-31125 affects vitejs:vite. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
vitejs:vite
affected versions
vitejs vite
  • affected>= 6.2.0 and < 6.2.4
  • affected>= 6.1.0 and < 6.1.3
  • affected>= 6.0.0 and < 6.0.13
  • affected>= 5.0.0 and < 5.4.16
  • affected< 4.5.11

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 4 GitHub proofs of concept · 1 Nuclei template

Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 23 Jan 2026 (SSVC 2.0.3).

timeline

  1. 31 Mar 2025Published
  2. 1 Apr 2025First proof-of-concept repository on GitHub (unvetted) · same day later
  3. 22 Jan 2026Added to CISA KEV (exploited in the wild) · 296 days (about 10 months) later
  4. 23 Jan 2026CISA SSVC assessment: exploitation active · 2 days later
  5. 23 Jan 2026CVE record last updated · same day later
  6. 12 Feb 2026CISA remediation due date (US federal agencies) · 19 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 264 days (about 9 months) later

also known as

GHSA-4r4m-qw57-chr8
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
3 references in the CVE record: 3 links
  • Linkgithub.com /vitejs/vite/security/advisories/GHSA-4r4m-qw57-chr8
  • Linkgithub.com /vitejs/vite/commit/59673137c45ac2bcfad1170d954347c1a17ab949
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-31125

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Nuclei templates: detection templates
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • OSV: advisory aliases and downstream package versions
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved