# CVE-2026-41612: Visual Studio Code Information Disclosure Vulnerability

> An attacker can exploit relative path traversal in the VS Code Live Preview extension to disclose local information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 10 Aug 2026

## What is CVE-2026-41612?

CVE-2026-41612 is a medium-severity path traversal vulnerability in Microsoft Visual Studio Code - Live Preview extension, published on 12 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Relative path traversal in Visual Studio Code allows an unauthorized attacker to disclose information locally.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-41612?

It affects 1 product.


Products: Microsoft Live Preview.

## How do I fix CVE-2026-41612?

No fix has been published for CVE-2026-41612 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41612 being exploited?

There is no known exploitation of CVE-2026-41612 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41612 and fix it if it is affected.

What it is: CVE-2026-41612 is a medium-severity path traversal vulnerability in Microsoft Visual Studio Code - Live Preview extension, published on 12 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41612 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio Code - Live Preview extension. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41612/ (Markdown: https://insights.sbomify.com/CVE-2026-41612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41612
- OSV: https://osv.dev/vulnerability/CVE-2026-41612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41612/
Summaries are generated and may contain mistakes; the official description above is the record.