CVE-2026-17310: IBM API Connect · Use of Hard-coded Cryptographic Key
Affects IBM API ConnectSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 7 Nov 2026, 05:20 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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– |
CPE configurations (2)
cpe:2.3:a:ibm:api_connect:12.1.0.0:*:*:*:*:*:*:*cpe:2.3:a:ibm:api_connect:12.1.1.2:*:*:*:*:*:*:*
AI-suggested
Until a fix is available, consider restricting network access to the affected API Connect instances to trusted parties only and monitor for any unusual activity related to cryptographic operations.
Description
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a vulnerability due to the use of a hard-coded cryptographic key. This flaw could allow a remote attacker to obtain sensitive information. The vulnerability is identified as CWE-321 and has a CVSS 3.1 base score of 6.5, indicating a medium severity level.