IBM BOB IDE · CVE-2026-5514 · AI agents & MCP
FIX → 2.0.4 ✓ verified
IBM Bob 2.0.3 exposes a session token in the account identifier field during account enumeration, so any installed extension can read it without user consent. A malicious extension could use that token to act as the user.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
IBM Bob IDE 2.0.3 exposes a session token to any installed extension through the account enumeration API, with no consent prompt. Only teams running Bob IDE 2.0.3 with extensions they do not fully trust are realistically exposed; those on 2.0.4 or with no extensions can skip it.
Not affected if no-extensions-installed
Who cares extensions, ibm-bob, vscode
2.0.3 is affected, upgrade to 2.0.4Upgrade to 2.0.4
IBM Bob 2.0.3 allows unauthorized extensions to retrieve session tokens via the authentication provider API. The token is exposed in the account identifier field during account enumeration, without requiring explicit user consent. This may allow malicious extensions to access sensitive session information and potentially perform unauthorized actions on behalf of the user.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade IBM Bob IDE to 2.0.4