IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to access sensitive configuration data and
Source GCVE Database
Not known to be exploited · CVSS 8.3 High.
Data as of 7 Nov 2026, 08:17 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 8.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:LExploitation 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 not a cloud service, remediation depends on vendor advisories. Organizations should monitor IBM's official security advisories for updates and apply patches or mitigations once released. Until then, restrict network access to the affected IBM API Connect management interfaces to trusted users only.
Description
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a vulnerability where missing authentication on a critical function allows remote attackers to access sensitive configuration data and perform unauthorized actions. This flaw affects the confidentiality, integrity, and availability of the affected systems.