Multiple Vulnerabilities in IBM API Connect
Only affects IBM API Connect 12.1.0.0 through 12.1.1.2 and 10.0.8.0 through 10.0.8.12 in certain non-default configurations. The listed fix is 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. Only in certain non-default configurations. The related feature must be enabled and not properly restricted, so customization content is evaluated as code.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.34% · 27th 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? →
- 16/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 has a flaw in its management service that lets a remote attacker who has low-level login access run arbitrary code, which could fully compromise the system's confidentiality, integrity, and availability. The bug can only be reached in certain non-default configurations where the customization feature is enabled and not properly restricted.
Read the original description
IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow arbitrary code to be executed by the management service in certain non-default configurations due to improper control of generation of code. Customization content may be evaluated as code, which is only possible where the related feature is enabled and not properly restricted.
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
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Only in certain non-default configurations. The related feature must be enabled and not properly restricted, so customization content is evaluated as code.Upgrade 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; From 10.0.8.0 · through 10.0.8.12
Evidence 2
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-105002
Is CVE-2026-105002 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?
Customization content can be evaluated as code by the API Connect management service. That can let arbitrary code run on the management service.Source: ibm.com, cve.org
Which versions are affected by CVE-2026-105002?
API Connect: from 12.1.0.0 through 12.1.1.2; from 10.0.8.0 through 10.0.8.12.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are 12.1.0.0 through 12.1.1.2 and 10.0.8.0 through 10.0.8.12. The issue only arises in non-default configurations where the related feature is enabled and not properly restricted, so check the installed version and that feature's settings.Source: ibm.com, cve.org