CVE
CVE-2025-65717
Ritwickdey · Live server
- First Reported
- Feb 18, 2026
- Latest Reported
- Feb 19, 2026
CVE Enrichment
- CVSS
- 4.3 MEDIUM
- EPSS
- 0.63%
- EPSS Percentile
- 50.40%
- CISA KEV
- Not listed
Description
An issue in Visual Studio Code Extensions Live Server v5.7.9 allows attackers to exfiltrate files via user interaction with a crafted HTML page.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- [email protected]
- Published
- 16-Feb-2026 23:19
- Last Modified
- 17-Jun-2026 16:55
- EPSS Date
- 2026-11-10
- CWE
- CWE-79, CWE-200, CWE-601
CVSS Vector
CVSS:3.1 AV:N /
AC:L /
PR:N /
UI:R /
S:U /
C:L /
I:N /
A:N
CNA Products / Version Status
- n/a · n/a
Source: CNA · [email protected]
Default status: unknown
n/a — affected
Affected Products / Versions
- ritwickdey / live_server
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 5.7.9
cpe:2.3:a:ritwickdey:live_server:*:*:*:*:*:visual_studio_code:*:*
References
Last enrichment sync: 10-Nov-2026 23:43
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (3)
- Three flaws received CVEs (CVE-2025-65717, CVE-2025-65715, CVE-2025-65716) with high CVSS scores enabling remote exploitation. Researchers Find Critical Flaws in Four VS Code Extensions With 128M+ Installs
- CVE-2025-65717 in Live Server (CVSS 9.1) can exfiltrate local files via localhost:5500. Flaws in Four VS Code Extensions Could Expose Local Files or Enable Code Execution
- CVE-2025-65717 in Live Server can be abused to steal local files by directing victims to a malicious webpage. Flaws in Popular VSCode Extensions Could Expose Developers to File Theft and Code Execution
CVE (2)
People (4)
MITRE ATT&CK (4)
Vendors (1)
Products (7)
Industries (1)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
