Multiple Vulnerabilities in IBM API Connect

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

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

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and tamper with configuration due to improper certificate validation.

Patch / fix

links 1

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

Is CVE-2026-17309 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.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

IBM API Connect

Classification

Weakness

CWE-295 Improper Certificate Validation

References

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

Sources

CVE List CVE-2026-17309
NVD CVE-2026-17309

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.