IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to inject
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 7 Nov 2026, 08:47 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 5.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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, users should monitor official IBM advisories for updates and consider restricting exposure of affected API Connect instances to untrusted networks.
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 a vulnerability where improper input validation could allow a remote attacker to inject platform credentials into outbound requests. This occurs because the validation check is not sufficiently strict, potentially exposing sensitive credentials.