VS Code 1.141.1 Fixes Copilot Agent, MCP Sandbox and Trust Bypasses
October 2026 Patch Tuesday brought 10 VS Code CVEs, including a prompt-injection path to agent hook files and an MCP server sandbox escape. Update to 1.141.1.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
October 2026 Patch Tuesday brought 10 VS Code CVEs, including a prompt-injection path to agent hook files and an MCP server sandbox escape. Update to 1.141.1.
Two AWS bulletins for Kiro IDE show a crafted repository steering the agent into editing configuration that Kiro then trusts. Upgrade to 1.0.242 and check ~/.kiro.
Five CVEs show Roo Code's command allowlist can be tricked into auto-approving denied shell commands. VulnCheck lists no fix, so the mitigation is configuration.
Aider loads .aider.conf.yml from the repository root, and a hostile repo can set test or lint commands that run through a shell. There is no fixed release yet.
The official TypeScript and Rust MCP SDKs trusted the MCP server to say where OAuth credentials should go. Upgrading fixes new sign-ins, but stored tokens need work too.
Two Flowise CVEs show the Custom MCP node running attacker-chosen npm packages. 3.1.4 fixes them, but Flowise reached end of life on 31 August 2026.
CVEs published in September for the mcp-atlassian server include a CVSS 10.0 auth bypass on its HTTP transport. Version 0.22.0 fixes it and changes defaults.
September's VS Code fixes include CVE-2026-81380, where prompt injection could make Copilot agent mode send environment variables out, and four agent network policy bypasses.
Elastic traced @apexacc/cli and @apexacc/audit to a fake Web3 accelerator. The CLI dropped stealers and sent the coding agent's model traffic and MCP calls to attacker servers.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.