IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a local attacker to obtain sensitive information due to the use
Source GCVE Database
Not known to be exploited · CVSS 8.7 High.
Data as of 7 Nov 2026, 08:04 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 8.7 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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– |
AI-suggested
Until a fix is available, restrict local access to trusted users only and monitor for vendor updates.
Description
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a vulnerability where a hard-coded cryptographic key is used. This flaw could allow a local attacker to obtain sensitive information. The vulnerability is classified as high severity with a CVSS score of 8.7.