IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow an authenticated user to obtain
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 7 Nov 2026, 07:48 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 4.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 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 6 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMAPI Connect | Affected
| Fixed in– |
Mavencom.ibm/api_connectpkg:maven/com.ibm/api_connectOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is released, organizations should review and restrict token issuance and usage policies to minimize exposure. Monitor IBM advisories for updates and apply patches promptly once available.
Description
IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 contain an authorization flaw that allows an authenticated user to obtain limited information about other organizations. This occurs because a token issued for a limited purpose is accepted where it should not be, potentially revealing organization names. The vulnerability has a medium severity rating with a CVSS score of 4.3.