CYBERSECURITYTRACKER
TRACKING7,472 stories in this site build1,582 vulnerability news stories in this site build
Vulnerabilities

CVE-2026-39365

Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker data as of: .

Detection and validation

Mapped metadata availability only. These signals do not change priority.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    Vite Dev Server - Path Traversal in Optimized Deps .map Handling. Check identifier: CVE-2026-39365.

    Open Nuclei metadata
  • Metasploit

    Not mapped by tracked sources.

What it is

Reported

Vite is a frontend tooling framework for JavaScript. From 6.0.0 to before 6.4.2, 7.3.2, and 8.0.5, the dev server’s handling of .map requests for optimized dependencies resolves file paths and calls readFile without restricting ../ segments in the URL. As a result, it is possible to bypass the server.fs.strict allow list and retrieve .map files located outside the project root, provided they can be parsed as valid source map JSON. This vulnerability is fixed in 6.4.2, 7.3.2, and 8.0.5.

Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:

What is affected

Reported

vitejs; vite. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:

Urgency and basis

Reported

Act · 445.6

Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:

Exploitation evidence

Reported

listed by a tracked exploitation catalog · VulnCheck KEV

Source reported · VulnCheck KEV added: · Source last updated: · Tracker data as of:

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Source remediation ↗

Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:

Evidence detail

Loading the full tracker evidence record…

Glossary