CVE-2026-45482

Copilot Chat path traversal could permit impersonation

Microsoft · Microsoft Visual Studio Code CoPilot Chat Extension

First documented disclosure · Review checkpoint

Summary

A pathname-confinement weakness could bypass an authentication feature.

Severity and exploitation evidence

High · 8.4/10 · CVSS 3.1. Severity source.

Exploitation not established: Microsoft marks Exploited: No. The reviewed material does not establish malicious exploitation against users.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Path traversal in the Copilot Chat extension crosses the intended restricted-directory boundary.

Conditions required

A local attack against the affected Copilot Chat component; the vendor vector requires neither attacker privileges nor user interaction.

Potential impact

Impersonation through the bypassed authentication feature.

Affected versions and configurations

Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 to before 1.123.2.

Fix and mitigation status

Microsoft Visual Studio Code CoPilot Chat Extension: 1.123.2.

Practical next steps

Install the vendor-listed corrected build for the applicable product and platform.

Operating lesson

Enforce the affected trust boundary independently of AI-generated content, caller identity and user-interface safeguards.

Evidence and limits

Historical backfill from a November 19–20 CVE update batch. Earliest reviewed public date is 2026-06-09; CNA initial publication is 2026-06-09, and current CNA datePublic is 2026-06-09T14: 00: 00.000Z. Microsoft CVSS 3.1 base score is 8.4; separate MSRC severity label: Important. The manufacturer marks Exploited: No in this reviewed entry. That is an attribution, not an assurance against future exploitation. The June 10 revision explains that the Chat extension merged into VS Code; 1.123.2 is the corrected application build, while the affected-range lower bound retains the historical extension numbering.

Sources