CVE-2026-5514: IBM Bob · Information Exposure
Affects IBM BobSource CVE Database V5
Not known to be exploited · CVSS 3.3 Low.
Data as of 13 Nov 2026, 22:02 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 3.3 |
|---|
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMBob | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:ibm:bob:2.0.3:*:*:*:*:*:*:*
Description
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.