Visual Studio Copilot and SSMS Remote Code Execution (CVE-2026-103572)
A researcher reports that a trailing-dot filename bypass in Microsoft.VisualStudio.Copilot.Core.dll let Copilot in Visual Studio and SQL Server Management Studio write to protected MCP and settings files, enabling arbitrary command…
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Recency not confirmed · what to check
We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.
Claim context: this brief is based on the researcher's write-up, and the full text of the Microsoft advisory was not checked.
One primary source; other links are context, not independent corroboration.
- Primary sourceembracethered.com
- Linked in sourceshipped the patch
- Linked in sourceother interesting quirks because of NTFS and Win32 differences
- Linked in sourceadd a malicious command as MCP server
- Linked in sourceSQL Copilot security issues
- Linked in sourceSlides: From SELECT to SYSADMIN. Hacking SQL Copilot in SSMS
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Recency not confirmed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
A researcher reports that a trailing-dot filename bypass in Microsoft.VisualStudio.Copilot.Core.dll let Copilot in Visual Studio and SQL Server Management Studio write to protected MCP and settings files, enabling arbitrary command execution. Writing a path ending in a dot passes validation but is canonicalized by Windows to the protected filename. The researcher also describes path traversal bypasses and a ripgrep path override, and says indirect prompt injection could trigger the chain. Microsoft classified the issue as Important with a CVSS of 8.8 and shipped a fix, though the researcher says no bounty was awarded.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; this brief is based on the researcher's write-up, and the full text of the Microsoft advisory was not checked.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; this brief is based on the researcher's write-up, and the full text of the Microsoft advisory was not checked.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
Trailing-dot filenames pass Copilot's protected-file check but are written to the protected target file by Windows.
Source: embracethered.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseThe flaw sits in a shared DLL, so Visual Studio and SSMS are both affected, including older versions such as Visual Studio 2022.
Source: embracethered.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphrasePath traversal inside the trusted Extensions directory reportedly allowed reading SSMS.isolation.ini and the user's settings file.
Source: embracethered.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseMicrosoft classified the issue as Important RCE with CVSS 8.8 and shipped a fix, but the researcher reports a $0 bounty.
Source: embracethered.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; this brief is based on the researcher's write-up, and the full text of the Microsoft advisory was not checked.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Embrace The Red published this item in its official feed. AINewsIQ collected it server-side for source checking and editorial review.
Source claims not independently checked; this brief is based on the researcher's write-up, and the full text of the Microsoft advisory was not checked.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
It shows that agent-facing security checks can be bypassed by Windows filename canonicalization quirks, so controls around AI agents must hold even when the agent is compromised or misaligned.
Limits and open questions
Source claims not independently checked; this brief is based on the researcher's write-up, and the full text of the Microsoft advisory was not checked.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →