IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information
Source GCVE Database
Not known to be exploited · CVSS 6.8 Medium.
Data as of 7 Nov 2026, 08:35 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 6.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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– |
AI-suggested
Since this is an authenticated attack vector, restricting access to trusted users and monitoring log file permissions may reduce risk.
Description
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a vulnerability where a remote authenticated attacker could obtain sensitive information due to the insertion of sensitive data into log files. This issue allows unauthorized access to sensitive information without impacting system integrity or availability.