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.77% · 55th 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? →
- 27/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
Summary
IBM API Connect is affected by a flaw in which authentication against a connected directory service is not sufficiently enforced. A remote attacker without logging in can obtain valid access tokens for other users and assume their identity.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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 a remote attacker to obtain valid access tokens for other users due to improper authentication. Authentication against a connected directory service is not sufficiently enforced, which could allow another user's identity to be assumed.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 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.now
- Posted on X 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-16720
Is CVE-2026-16720 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?
Authentication against a connected directory service is not sufficiently enforced, so an attacker may be able to obtain valid access tokens for other users and assume another user's identity.Source: ibm.com, cve.org
Which versions are affected by CVE-2026-16720?
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?
IBM API Connect 12.1.0.0 through 12.1.1.2 and 10.0.8.0 through 10.0.8.12 are listed as affected. The issue applies where a connected directory service is used for authentication, so check your API Connect version and whether a directory service is configured for authentication.Source: ibm.com, cve.org