1sealsemantic last-mile verification

Research / Finding

Workspace trust for MCP servers

F-VSCODE-MCP-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
CVE-2026-21518CVEmicrosoft/vscode

Workspace trust for MCP servers

Fixed in: VS Code 1.109.1

patched
details
Finding IDs
F-VSCODE-MCP-001
CVE
CVE-2026-21518
GHSA
GHSA-6xq8-9qf3-p6qv
Status
patched
Fixed in
VS Code 1.109.1
Note
GHSA-6xq8-9qf3-p6qv · metadata correction requested
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
CVE registry state
PUBLISHED
CVE state checked
Upstream title
Workspace trust for MCP servers
Upstream publication
Upstream updated
Metadata fetched
Upstream @1seal credit
No structured @1seal credit in this snapshot; textual acknowledgements may exist.

F-VSCODE-MCP-001: Access control. The recorded report concerns bypassing the MCP workspace trust boundary. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-VSCODE-MCP-001

Security area (1seal assessment): Authorization. The recorded report concerns bypassing the MCP workspace trust boundary. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.