IBM BOB SHELL · CVE-2026-9764 · AI agents & MCP
FIX → 2.0.2 ✓ verified
Per IBM's bulletin, opening an untrusted repository in IBM Bob Shell 1.0.4 to 2.0.1 could automatically run MCP servers defined in the repository's workspace configuration without explicit user consent, giving the attacker code execution. IBM fixed it in 2.0.2 with a Workspace Folder Trust feature that blocks workspace-defined MCP servers and other workspace configuration until the user trusts the repository.
first public Nov 8, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running IBM Bob Shell 1.0.4 through 2.0.1 who opens a repository from an outside or untrusted source. The repository's workspace-defined MCP server configuration is started without explicit consent, so the attacker's code runs on the developer's machine. Teams that open only repositories they trust, or that run 2.0.2 or later, can skip it. IBM lists Bob Shell only; the bulletin does not name the Bob IDE.
Not affected if only-trusted-repos
Who cares bob-shell, ibm-bob, mcp, untrusted-repository
1.0.4 through 2.0.1 are affectedIBM Bob 1.0.4 through 2.0.1 could allow a remote attacker to inject arbitrary code on the system, due to the improper control of user input code.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 2.0.2
Upgrade IBM Bob Shell to 2.0.2 or later (Workspace Folder Trust blocks workspace-defined MCP servers until the repo is trusted).