Multiple Vulnerabilities in IBM API Connect
Affects IBM API Connect 12.1.0.0 through 12.1.1.2 when service definitions are imported. The fix is in 12.1.1.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 12.1.1.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Service definitions are imported
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.36% · 29th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery. When service definitions are imported, references to external resources are not sufficiently restricted, so the server could be made to request resources it should not access.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Service definitions are importedUpgrade to a fixed version: 12.1.1.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- IBM API Connect
From 12.1.0.0 · through 12.1.1.2
Evidence 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-17188
Is CVE-2026-17188 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When service definitions are imported, the server does not sufficiently restrict references to external resources. A remote authenticated attacker can make the server request resources it should not access, which can expose sensitive information (server-side request forgery).Source: ibm.com, cve.org
Which versions are affected by CVE-2026-17188?
API Connect: from 12.1.0.0 through 12.1.1.2.Source: cve.now feed data