---
title: "CVE-2026-102238: Visual Studio Code - Path Traversal"
description: "Visual Studio Code contains a path traversal vulnerability caused by improper limitation of a pathname to a restricted directory, letting unauthorized attackers execute code over a network, exploit requires network access."
url: https://panop.io/threat-heartbeat/CVE-2026-102238/
---

# CVE-2026-102238 Visual Studio Code - Path Traversal

Visual Studio Code contains a path traversal vulnerability caused by improper limitation of a pathname to a restricted directory, letting unauthorized attackers execute code over a network, exploit requires network access.

CVSS base score 9.6 /10

Critical

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.65% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-102238)

## Details

Type

Path Traversal

Impact

Remote Code Execution

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Published

13 October 2026

Updated

15 October 2026

Weakness

[CWE-22](https://cwe.mitre.org/data/definitions/22.html)

## Vendor fix

Update to the latest version of Visual Studio Code.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-102238](https://nvd.nist.gov/vuln/detail/CVE-2026-102238)
- [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-102238](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-102238)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)