IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to access internal network resources and
Source GCVE Database
Not known to be exploited · CVSS 7.2 High.
Data as of 7 Nov 2026, 07:36 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 7.2 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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– |
Mavencom.ibm/api_connectpkg:maven/com.ibm/api_connectOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, organizations should consider implementing network-level controls to restrict outbound requests from the affected server to internal addresses and monitor for suspicious activity related to SSRF attempts.
Description
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a server-side request forgery (SSRF) vulnerability that allows a remote attacker to bypass protections blocking requests to internal network addresses. This flaw enables the attacker to make the server contact internal services and retrieve partial responses, potentially exposing sensitive information.