Multiple Vulnerabilities in IBM API Connect

published 2026-11-07 2d ago modified 2026-11-07 2d ago also EUVD-2026-118658

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits: 0; none known

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 authenticated attacker to bypass security restrictions and access unauthorized analytics queries due to improper input validation. Request parameters are not validated sufficiently, which could allow restrictions on analytics data to be circumvented.

Patch / fix

links 2

ibm.com/support/pages/node/7295635 advisory
ibm.com/support/pages/node/7295637 advisory

Is CVE-2026-17225 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected products

IBM API Connect

Classification

Weakness

CWE-235 Improper Handling of Extra Parameters

References

ibm.com /support/pages/node/7295635
vendor-advisory, patch
ibm.com /support/pages/node/7295637
vendor-advisory, patch

Sources

CVE List CVE-2026-17225
NVD CVE-2026-17225

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.