CVE-2026-41109

Copilot could bypass approval for protected file writes

Microsoft · Visual Studio Code

First documented disclosure · Review checkpoint

Summary

Injected content could bypass path checks and approval for sensitive locations.

Severity and exploitation evidence

High · 8.8/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

Injection through external content defeats the path-validation boundary.

Conditions required

A user opens a maliciously crafted package in the coding environment.

Potential impact

Protected files can be changed without the user’s knowledge or approval.

Affected versions and configurations

Visual Studio Code: 1.0.0 to before 1.128.1.

Fix and mitigation status

Visual Studio Code: 1.128.1.

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-05-12; CNA initial publication is 2026-05-12, and current CNA datePublic is 2026-07-14T14: 00: 00.000Z. Microsoft CVSS 3.1 base score is 8.8; 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 May CVRF lists 1.119.1, but the July CVRF and current CNA list 1.128.1. Both original entries exist for the same CVE; this row uses the later current fix requirement and does not treat the May fix as complete.

Sources