| CVE-2026-17337 | HIGH | 7.4 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass authentication… | 2026-11-07 |
| CVE-2026-17338 | CRITICAL | 9.1 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive info… | 2026-11-07 |
| CVE-2026-17339 | CRITICAL | 9.1 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to access or delete reso… | 2026-11-07 |
| CVE-2026-17340 | CRITICAL | 9.8 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to execute arbitrary code due to a pat… | 2026-11-07 |
| CVE-2026-17341 | HIGH | 7.2 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to perform server-side request forgery… | 2026-11-07 |
| CVE-2026-17342 | CRITICAL | 9.9 | 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 at… | 2026-11-07 |
| CVE-2026-17343 | HIGH | 8.1 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass authorization … | 2026-11-07 |
| CVE-2026-17344 | CRITICAL | 9.3 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to… | 2026-11-07 |
| CVE-2026-17345 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17352 | HIGH | 8.5 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive info… | 2026-11-07 |
| CVE-2026-17353 | CRITICAL | 9.6 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive info… | 2026-11-07 |
| CVE-2026-17354 | CRITICAL | 9.9 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to perform arbitrary fil… | 2026-11-07 |
| CVE-2026-17355 | HIGH | 8.2 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive info… | 2026-11-07 |
| CVE-2026-17356 | HIGH | 8.7 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a local attacker to obtain sensitive information due to … | 2026-11-07 |
| CVE-2026-17357 | HIGH | 7.6 | 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 at… | 2026-11-07 |
| CVE-2026-17358 | HIGH | 8.2 | 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 at… | 2026-11-07 |
| CVE-2026-17359 | CRITICAL | 9.9 | 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 at… | 2026-11-07 |
| CVE-2026-17360 | CRITICAL | 9.8 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to gain full administrative control du… | 2026-11-07 |
| CVE-2026-17361 | HIGH | 7.7 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive info… | 2026-11-07 |
| CVE-2026-17363 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17365 | HIGH | 8.5 | 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 at… | 2026-11-07 |
| CVE-2026-17366 | MEDIUM | 5.0 | 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 at… | 2026-11-07 |
| CVE-2026-17367 | MEDIUM | 5.4 | 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 at… | 2026-11-07 |
| CVE-2026-17368 | MEDIUM | 6.8 | 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 at… | 2026-11-07 |
| CVE-2026-17369 | MEDIUM | 5.4 | 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 forc… | 2026-11-07 |
| CVE-2026-17370 | MEDIUM | 6.4 | 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 at… | 2026-11-07 |
| CVE-2026-17371 | MEDIUM | 5.0 | 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 at… | 2026-11-07 |
| CVE-2026-17372 | MEDIUM | 6.4 | 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 at… | 2026-11-07 |
| CVE-2026-17373 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17374 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17375 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17376 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17377 | MEDIUM | 5.0 | 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 at… | 2026-11-07 |
| CVE-2026-17378 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17379 | HIGH | 7.4 | 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 bypa… | 2026-11-07 |
| CVE-2026-17380 | HIGH | 8.5 | 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 at… | 2026-11-07 |
| CVE-2026-17381 | HIGH | 8.5 | 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 at… | 2026-11-07 |
| CVE-2026-17382 | HIGH | 8.5 | 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 at… | 2026-11-07 |
| CVE-2026-17383 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17384 | HIGH | 8.5 | IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a remote authenticated attacker to obtain sensitive inf… | 2026-11-07 |
| CVE-2026-17385 | HIGH | 8.5 | 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 at… | 2026-11-07 |
| CVE-2026-17386 | HIGH | 8.1 | IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a remote attacker to gain full administrative control d… | 2026-11-07 |
| CVE-2026-17387 | HIGH | 7.7 | 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 at… | 2026-11-07 |
| CVE-2026-17388 | HIGH | 8.5 | 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 at… | 2026-11-07 |
| CVE-2026-17389 | MEDIUM | 5.3 | 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 obta… | 2026-11-07 |
| CVE-2026-17390 | MEDIUM | 6.4 | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow an authenticated user to … | 2026-11-07 |
| CVE-2026-17391 | MEDIUM | 6.3 | 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 at… | 2026-11-07 |
| CVE-2026-17392 | CRITICAL | 9.9 | 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 at… | 2026-11-07 |
| CVE-2026-17393 | MEDIUM | 5.1 | IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a local attacker to obtain sensitive information due to… | 2026-11-07 |
| CVE-2026-17394 | CRITICAL | 9.6 | 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 at… | 2026-11-07 |