Multiple Vulnerabilities in IBM API Connect
- Exploited
- No known exploitation
- Fix
- Fixed in 12.1.1.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 12.1.1.3.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.39% · 33rd 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? →
- 28/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? →
- Unclear
- 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
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow an authenticated attacker to send unauthorized requests from the system due to server-side request forgery. This could be used to enumerate network resources or to support further attacks.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- 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 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 12.1.1.3.
Timeline
- CVE published
- First seen by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
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-19128
Is CVE-2026-19128 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?
The flaw is a server-side request forgery bug. An authenticated attacker can make the system send unauthorized requests, which could be used to enumerate network resources or support further attacks.Source: ibm.com, cve.org
Which versions are affected by CVE-2026-19128?
API Connect: from 12.1.0.0 through 12.1.1.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions of IBM API Connect from 12.1.0.0 through 12.1.1.2 are affected. To check, look up the installed API Connect version in your deployment. No specific configuration is listed as a condition.Source: ibm.com, cve.org