cpe:2.3:a:ibm:api_connect:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
13critical22high44medium1low
updated 2026-10-28
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2018-1932US | medium4.9 | 3.23% (88th) | Exploit | ✗no fix | 2019-01-08 | 5.0.0.0 → 5.0.8.4 |
| CVE-2025-13915US | — | 9.01% (95th) | — | ✗no fix | 2025-12-26 | 2 versions |
| CVE-2019-4382US | medium5.3OT elevated | 7.83% (95th) | — | ✗no fix | 2019-06-25 | 5.0.0.0 → 5.0.8.6 |
| CVE-2019-4202US | critical10.0 | 4.22% (91st) | — | ✗no fix | 2019-04-15 | 5.0.0.0 → 5.0.8.6 |
| CVE-2018-1778US | high8.1 | 3.45% (89th) | — | ✗no fix | 2018-12-20 | 2 versions |
| CVE-2018-2011US | medium5.3 | 2.77% (86th) | — | ✗no fix | 2019-06-25 | 2018.1.0 → 2018.4.1.5 |
| CVE-2018-1469US | critical9.8 | 2.73% (86th) | — | ✗no fix | 2018-04-04 | 3 versions |
| CVE-2019-4155US | critical9.8 | 2.63% (85th) | — | ✗no fix | 2019-04-08 | 2018.1.0 → 2018.4.1.3 |
| CVE-2019-4460US | high7.5 | 2.57% (85th) | — | ✗no fix | 2019-08-20 | 5.0.0.0 → 5.0.8.6 |
| CVE-2018-1779US | high7.5 | 2.49% (85th) | — | ✗no fix | 2018-11-20 | 2018.1.0 → 2018.3.7 |
| CVE-2016-1000232US | medium5.3 | 2.36% (84th) | — | ✗no fix | 2018-09-05 | 3 versions |
| CVE-2017-1322US | high8.2 | 2.34% (83rd) | — | ✗no fix | 2017-06-27 | 11 versions |
| CVE-2018-1973US | high7.2 | 2.30% (83rd) | — | ✗no fix | 2018-12-20 | 5.0.0.0 → 5.0.8.4 |
| CVE-2019-4008US | critical9.8 | 2.27% (83rd) | — | ✗no fix | 2019-02-07 | 2018.1.0 → 2018.4.1.1 |
| CVE-2018-1546US | medium4.3 | 2.18% (82nd) | — | ✗no fix | 2018-07-06 | 5.0.0.0 → 5.0.8.3 |
| CVE-2017-1379US | high7.5 | 2.03% (81st) | — | ✗no fix | 2017-06-15 | 12 versions |
| CVE-2019-4052US | high7.5 | 1.91% (80th) | — | ✗no fix | 2019-03-22 | 2018.1.0 → 2018.4.1.2 |
| CVE-2018-2013US | medium5.3 | 1.76% (78th) | — | ✗no fix | 2019-06-25 | 2018.1.0 → 2018.4.1.5 |
| CVE-2018-1638US | high8.1 | 1.75% (78th) | — | ✗no fix | 2018-07-31 | 5.0.0.0 → 5.0.8.3 |
| CVE-2017-1328US | medium5.3 | 1.74% (78th) | — | ✗no fix | 2017-06-27 | 10 versions |
| CVE-2018-1784US | critical9.8 | 1.73% (77th) | — | ✗no fix | 2018-12-20 | 5.0.0.0 → 5.0.8.4 |
| CVE-2019-4203US | critical9.8 | 1.73% (77th) | — | ✗no fix | 2019-04-15 | 5.0.0.0 → 5.0.8.6 |
| CVE-2020-4638US | high7.2 | 1.71% (77th) | — | ✗no fix | 2020-09-03 | 2018.4.1.0 → 2018.4.1.12 |
| CVE-2019-4051US | medium5.3 | 1.70% (77th) | — | ✗no fix | 2019-04-08 | 2018.1.0 → 2018.4.1.3 |
| CVE-2016-3012US | high7.5 | 1.67% (77th) | — | ✗no fix | 2016-12-01 | ≤ 5.0.2.0 |
| CVE-2018-1976US | medium4.9 | 1.67% (77th) | — | ✗no fix | 2019-01-29 | 5.0.0.0 → 5.0.8.4 |
| CVE-2018-2009US | medium6.5 | 1.65% (76th) | — | ✗no fix | 2019-03-11 | 2018.1.0 → 2018.4.1.0 |
| CVE-2021-29715US | critical9.1 | 1.64% (76th) | — | ✗no fix | 2021-08-26 | 5.0.0.0 → 5.0.8.11 |
| CVE-2019-4402US | high7.5 | 1.64% (76th) | — | ✗no fix | 2019-08-20 | 2018.1.0 → 2018.4.1.6 |
| CVE-2018-2015US | medium6.1 | 1.59% (76th) | — | ✗no fix | 2019-05-02 | 2018.1.0 → 2018.4.1.4 |
| CVE-2017-1161US | high7.3 | 1.49% (74th) | — | ✗no fix | 2017-04-17 | = 5.0.6.0 |
| CVE-2017-1556US | medium6.5 | 1.46% (73rd) | — | ✗no fix | 2017-09-13 | 3 versions |
| CVE-2018-1389US | medium6.5 | 1.45% (73rd) | — | ✗no fix | 2018-04-30 | 5.0.0.0 → 5.0.8.2 |
| CVE-2019-4437US | medium5.3 | 1.45% (73rd) | — | ✗no fix | 2019-08-20 | 2018.1.0 → 2018.4.1.6 |
| CVE-2019-4600US | medium5.3 | 1.43% (73rd) | — | ✗no fix | 2019-10-29 | 5.0.0.0 → 5.0.8.7 |
| CVE-2019-4256US | high7.5 | 1.32% (71st) | — | ✗no fix | 2019-05-29 | 5.0.0.0 → 5.0.8.6 |
| CVE-2018-1548US | medium4.3 | 1.30% (70th) | — | ✗no fix | 2018-07-09 | 2018.1.0.0 → 2018.2.4 |
| CVE-2018-1789US | critical9.9 | 1.23% (69th) | — | ✗no fix | 2018-09-07 | 2018.1.0 → 2018.3.4 |
| CVE-2017-1386US | medium5.9 | 1.16% (67th) | — | ✗no fix | 2017-07-31 | 11 versions |
| CVE-2020-4346US | medium5.3OT elevated | 1.10% (65th) | — | ✗no fix | 2020-05-12 | 2018.4.1.0 → 2018.4.1.10 |
| CVE-2018-1774US | high7.8 | 1.06% (64th) | — | ✗no fix | 2018-11-09 | 2 versions |
| CVE-2020-4337US | medium6.5 | 1.05% (64th) | — | ✗no fix | 2020-09-03 | 2018.4.1.0 → 2018.4.1.12 |
| CVE-2018-1859US | medium4.7 | 1.04% (64th) | — | ✗no fix | 2019-01-04 | 5.0.0.0 → 5.0.8.4 |
| CVE-2018-2007US | high7.5 | 0.97% (62nd) | — | ✗no fix | 2019-04-29 | 2018.1.0 → 2018.4.1.2 |
| CVE-2018-1532US | medium4.3 | 0.96% (61st) | — | ✗no fix | 2018-05-31 | 5.0.0.0 → 5.0.8.2 |
| CVE-2018-1991US | low2.7 | 0.96% (61st) | — | ✗no fix | 2019-05-22 | 5.0.0.0 → 5.0.8.6 |
| CVE-2018-1468US | medium4.3 | 0.95% (61st) | — | ✗no fix | 2018-05-02 | 2 versions |
| CVE-2017-1785US | medium4.3 | 0.95% (61st) | — | ✗no fix | 2018-02-07 | 5 versions |
| CVE-2020-4706US | medium5.4 | 0.94% (61st) | — | ✗no fix | 2021-08-17 | 5.0.0.0 → 5.0.8.10 |
| CVE-2018-1430US | medium5.4 | 0.93% (60th) | — | ✗no fix | 2018-04-30 | 5.0.0.0 → 5.0.8.2 |
showing 50 of 81