How severe is GHSA-4r4m-qw57-chr8?

GHSA-4r4m-qw57-chr8 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-4r4m-qw57-chr8?

GHSA-4r4m-qw57-chr8 affects the following packages: vite (npm), vite (npm), vite (npm), vite (npm), vite (npm). Ecosystems affected: npm.

How do I fix GHSA-4r4m-qw57-chr8?

Update vite to version 6.2.4 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-4r4m-qw57-chr8 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-4r4m-qw57-chr8, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-4r4m-qw57-chr8?

GHSA-4r4m-qw57-chr8 has an EPSS (Exploit Prediction Scoring System) score of 83.2%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-4r4m-qw57-chr8 in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-4r4m-qw57-chr8 (Vite Vitejs Improper Access Control Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-01-22. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-02-12. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-4r4m-qw57-chr8?

GHSA-4r4m-qw57-chr8 is classified as Information Exposure (CWE-200), CWE-284 (CWE-284). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-4r4m-qw57-chr8?

A Nuclei detection template exists for GHSA-4r4m-qw57-chr8, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-4r4m-qw57-chr8 published, and has it been updated?

GHSA-4r4m-qw57-chr8 was published on March 31, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-01-22 — agencies required to remediate by 2026-02-12

📦 npm

GHSA-4r4m-qw57-chr8

MEDIUM

Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` query

Also known asCVE-2025-31125

Published

Mar 31, 2025

Updated

Feb 4, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

83.2%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

📦vite📦vite📦vite📦vite📦vite

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The contents of arbitrary files can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected.

Details

base64 encoded content of non-allowed files is exposed using ?inline&import (originally reported as ?import&?inline=1.wasm?init)
content of non-allowed files is exposed using ?raw?import

/@fs/ isn't needed to reproduce the issue for files inside the project root.

PoC

Original report (check details above for simplified cases):

The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice

$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run dev

Example full URL http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vite`	≥ 6.2.0&&< 6.2.4	6.2.4
📦npm	`vite`	≥ 6.1.0&&< 6.1.3	6.1.3
📦npm	`vite`	≥ 6.0.0&&< 6.0.13	6.0.13
📦npm	`vite`	≥ 5.0.0&&< 5.4.16	5.4.16
📦npm	`vite`	all versions	4.5.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

sunhuiHi666/CVE-2025-31125

Vite 任意文件读取漏洞POC

⭐ 6🍴 0Jun 2026

Frequently Asked Questions

### Summary The contents of arbitrary files can be returned to the browser. ### Impact Only apps explicitly exposing the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) are affected. ### Details - base64 encoded content of non-allowed files is exposed using `?inline&import` (originally reported as `?import&?inline=1.wasm?init`) - content of non-allowed files is exposed using `?raw?import` `/@fs/` isn't needed to reproduce the issue for files inside the project root. ### PoC Original report (check

O3 Security · Impact-Aware SCA

Is GHSA-4r4m-qw57-chr8 in your stack?

O3 detects GHSA-4r4m-qw57-chr8 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works