| CVE-2026-17098 | 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-17108 | 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-17112 | 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-17114 | 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-17117 | 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-17128 | MEDIUM | 6.8 | 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-17129 | HIGH | 7.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-17131 | 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-17132 | CRITICAL | 9.9 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary SQL… | 2026-11-07 |
| CVE-2026-17134 | CRITICAL | 9.9 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary SQL… | 2026-11-07 |
| CVE-2026-17137 | MEDIUM | 4.0 | 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-17139 | 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-17140 | LOW | 3.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-17143 | MEDIUM | 4.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-17144 | MEDIUM | 4.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-17146 | 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-17147 | 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-17150 | 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-17154 | MEDIUM | 5.4 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to perform cross-site sc… | 2026-11-07 |
| CVE-2026-17155 | MEDIUM | 5.4 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary scr… | 2026-11-07 |
| CVE-2026-17158 | 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-17167 | MEDIUM | 4.3 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to falsify audit log inf… | 2026-11-07 |
| CVE-2026-17172 | 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-17187 | 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-17188 | 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-17190 | HIGH | 8.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-17202 | MEDIUM | 5.3 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to enumerate usernames due to observab… | 2026-11-07 |
| CVE-2026-17211 | MEDIUM | 4.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-17214 | MEDIUM | 4.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 attacker to bypa… | 2026-11-07 |
| CVE-2026-17215 | MEDIUM | 4.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-17225 | 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-17228 | 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-17230 | 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-17231 | MEDIUM | 5.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 attacker to obta… | 2026-11-07 |
| CVE-2026-17232 | MEDIUM | 6.1 | 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-17233 | 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-17236 | 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-17237 | 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-17238 | 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-17239 | CRITICAL | 9.9 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary cod… | 2026-11-07 |
| CVE-2026-17240 | MEDIUM | 6.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 attacker to bypa… | 2026-11-07 |
| CVE-2026-17241 | MEDIUM | 6.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-17244 | 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 authenticated at… | 2026-11-07 |
| CVE-2026-17278 | CRITICAL | 9.8 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to gain unauthorized access to sensiti… | 2026-11-07 |
| CVE-2026-17279 | 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-17280 | HIGH | 8.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 attacker to perf… | 2026-11-07 |
| CVE-2026-17281 | 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-17282 | 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-17283 | 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-17284 | HIGH | 7.1 | 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 |