| CVE-2026-16711 |
Multiple Vulnerabilities in IBM API Connect
|
5.3
Medium
|
Nov 7, 2026 |
| CVE-2026-16710 |
Multiple Vulnerabilities in IBM API Connect
|
5.8
Medium
|
Nov 7, 2026 |
| CVE-2026-16709 |
Multiple Vulnerabilities in IBM API Connect
|
8.7
High
|
Nov 7, 2026 |
| CVE-2026-16679 |
IBM API Connect Path Traversal
|
4.3
Medium
|
Nov 7, 2026 |
| CVE-2026-108178 |
Multiple Vulnerabilities in IBM API Connect
|
4.2
Medium
|
Nov 7, 2026 |
| CVE-2026-105459 |
Multiple Vulnerabilities in IBM API Connect
|
6.8
Medium
|
Nov 7, 2026 |
| CVE-2026-105002 |
Multiple Vulnerabilities in IBM API Connect
|
7.5
High
|
Nov 7, 2026 |
| CVE-2026-17362 |
Multiple Vulnerabilities in IBM API Connect
|
9.8
Critical
|
Nov 7, 2026 |
| CVE-2026-9074 |
IBM API Connect 10.0.8.0 through 10.0.8.9 and 12.1.0.0 through 12.1.0.3 contains an unauthenticated SQL injection…
|
9.1
Critical
|
Jul 8, 2026 |
| CVE-2026-3144 |
IBM API Connect 12.1.0.0 through 12.1.0.3 uses default credentials which could allow an attacker to gain unauthorized…
|
8.1
High
|
Jul 8, 2026 |
| CVE-2025-13915 |
IBM API Connect 10.0.8.0 through 10.0.8.5, and 10.0.11.0 could allow a remote attacker to bypass authentication…
|
9.8
Critical
|
Dec 26, 2025 |
| CVE-2023-47722 |
IBM API Connect V10.0.5.3 and V10.0.6.0 stores user credentials in browser cache which can be read by a local user
|
6.2
Medium
|
Dec 9, 2023 |
| CVE-2023-28522 |
IBM API Connect V10 could allow an authenticated user to perform actions that they should not have access to
|
4.3
Medium
|
May 12, 2023 |
| CVE-2022-34350 |
IBM API Connect 10.0.0.0 through 10.0.5.0, 10.0.1.0 through 10.0.1.7, and 2018.4.1.0 through 2018.4.1.20 is vulnerable…
|
5.3
Medium
|
Feb 8, 2023 |
| CVE-2021-38997 |
IBM API Connect V10.0.0.0 through V10.0.5.0, V10.0.1.0 through V10.0.1.7, and V2018.4.1.0 through 2018.4.1.19 is…
|
5.4
Medium
|
Dec 1, 2022 |
| CVE-2021-29772 |
IBM API Connect 5.0.0.0 through 5.0.8.11 could allow a user to potentially inject code due to unsanitized user input
|
5.6
Medium
|
Aug 26, 2021 |
| CVE-2021-29715 |
IBM API Connect 5.0.0.0 through 5.0.8.11 could alllow a remote user to obtain sensitive information or conduct denial of…
|
6.5
Medium
|
Aug 26, 2021 |
| CVE-2020-4706 |
IBM API Connect 5.0.0.0 through 5.0.8.10 is vulnerable to HTTP header injection, caused by improper validation of…
|
5.4
Medium
|
Aug 17, 2021 |
| CVE-2020-4707 |
IBM API Connect 5.0.0.0 through 5.0.8.11 is vulnerable to cross-site scripting
|
5.4
Medium
|
Aug 4, 2021 |
| CVE-2021-20440 |
IBM API Connect 10.0.0.0, and 2018.4.1.0 through 2018.4.1.13 does not restrict member registration to the intended…
|
6.4
Medium
|
Mar 15, 2021 |
| CVE-2020-4903 |
IBM API Connect V10 and V2018 could allow an attacker who has intercepted a registration invitation link to…
|
4.8
Medium
|
Mar 8, 2021 |
| CVE-2020-4695 |
IBM API Connect V10 is impacted by insecure communications during database replication
|
5.9
Medium
|
Mar 8, 2021 |
| CVE-2020-4828 |
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to web cache poisoning,…
|
6.5
Medium
|
Feb 4, 2021 |
| CVE-2020-4827 |
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to cross-site request forgery…
|
4.3
Medium
|
Feb 4, 2021 |
| CVE-2020-4826 |
IBM API Connect 10.0.0.0 through 10.0.1.0 and 2018.4.1.0 through 2018.4.1.13 is vulnerable to cross-site request forgery…
|
4.3
Medium
|
Feb 4, 2021 |