Skip to main content
CVE-2025-58751VulnerabilityPublished

CVE-2025-58751: vitejs vite · Path Traversal

Affects vitejs viteSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 2.3 Low : upgrade to 5.4.20 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.4.20
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Sep 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade vitejs vite to 5.4.20.

Affected software

ProductAffectedFixed in
vitejs viteAffected
  • <5.4.20
Fixed in
  • 5.4.20

AI-suggested

A fix is available in vite version 5.4.20 and later. Users should upgrade to vite >=5.4.20 to remediate this vulnerability. Until then, avoid exposing the vite dev server to the network or avoid using symlinks in the public directory. Patch status is confirmed by the affectedVersions field indicating versions <5.4.20 are vulnerable.

Description

CVE-2025-58751 is a path traversal vulnerability in the vitejs vite development server affecting versions prior to 5.4.20. It allows an attacker to bypass server filesystem restrictions and access files outside the intended public directory when certain conditions are met, including exposing the dev server to the network, using the public directory feature, and having a symlink in the public directory. The vulnerability arises from improper path normalization and checking in the middleware serving public files, enabling traversal via crafted requests.

References

Community reviews

Loading reviews…