Multiple Vulnerabilities in IBM API Connect
- Exploited
- No known exploitation
- Fix
- Fixed in v12.1.1.3
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: v12.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.54% · 45th 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? →
- 18/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 is affected by multiple vulnerabilities. A remote attacker with low-privilege login credentials can exploit an authorization bypass through user-controlled keys to read sensitive information and modify arbitrary documents.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information and modify arbitrary documents due to authorization bypass through user-controlled keys.
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
- Severity9.9/10CVSS 9.9
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Upgrade to a fixed version: v12.1.1.3.
Timeline
- CVE published
- First seen by cve.now
- Posted on X 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-17049
Is CVE-2026-17049 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
Which versions are affected by CVE-2026-17049?
API Connect: from 12.1.0.0 through 12.1.1.2.Source: cve.now feed data
How do I fix CVE-2026-17049?
Upgrade IBM API Connect to v12.1.1.3, the fixed release. IBM strongly recommends addressing the vulnerability now by upgrading to v12.1.1.3.Source: cve.org