Browse All CVEs
50,445 vulnerabilities.
| CVE | Severity | CVSS | EPSS | First Seen | Flags | Description |
|---|---|---|---|---|---|---|
CVE-2026-17332 |
high | 8.7 | 0.0027 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to bypass security | |
CVE-2026-17331 |
high | 7.5 | 0.0051 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to read arbitrary | |
CVE-2026-17330 |
high | 8.5 | 0.0036 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17329 |
critical | 9.3 | 0.0042 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17328 |
high | 8.5 | 0.0038 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17327 |
high | 8.5 | 0.0036 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17326 |
high | 8.1 | 0.0058 | 2026-11-07 | 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 rem | |
CVE-2026-17325 |
high | 8.5 | 0.0036 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17324 |
high | 8.3 | 0.0046 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to access sensitiv | |
CVE-2026-17323 |
high | 8.2 | 0.0058 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17322 |
high | 7.1 | 0.0015 | 2026-11-07 | 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 loc | |
CVE-2026-17321 |
high | 8.1 | 0.0045 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to d | |
CVE-2026-17320 |
high | 7.7 | 0.0042 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17319 |
high | 7.1 | 0.0021 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to m | |
CVE-2026-17318 |
high | 7.7 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17317 |
medium | 6.4 | 0.0037 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to a | |
CVE-2026-17316 |
high | 7.2 | 0.0032 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to perform server- | |
CVE-2026-17315 |
medium | 5.8 | 0.0038 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17314 |
medium | 5.0 | 0.0033 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17313 |
critical | 9.8 | 0.0078 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17312 |
medium | 5.4 | 0.0016 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to force a user to | |
CVE-2026-17311 |
high | 7.1 | 0.0041 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to m | |
CVE-2026-17310 |
medium | 6.5 | 0.0032 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17309 |
high | 8.0 | 0.0015 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17308 |
medium | 6.8 | 0.0014 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17307 |
medium | 6.5 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17306 |
high | 8.6 | 0.0043 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitiv | |
CVE-2026-17305 |
medium | 5.5 | 0.0032 | 2026-11-07 | 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 rem | |
CVE-2026-17304 |
medium | 6.5 | 0.0031 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to o | |
CVE-2026-17303 |
medium | 6.4 | 0.0029 | 2026-11-07 | 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 rem | |
CVE-2026-17302 |
medium | 5.0 | 0.0033 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to p | |
CVE-2026-17301 |
critical | 9.8 | 0.0041 | 2026-11-07 | 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 un | |
CVE-2026-17299 |
high | 8.1 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17298 |
high | 7.7 | 0.0050 | 2026-11-07 | 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 rem | |
CVE-2026-17297 |
critical | 9.6 | 0.0061 | 2026-11-07 | 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 rem | |
CVE-2026-17296 |
critical | 9.6 | 0.0045 | 2026-11-07 | 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 rem | |
CVE-2026-17295 |
high | 7.7 | 0.0070 | 2026-11-07 | 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 rem | |
CVE-2026-17294 |
high | 8.5 | 0.0037 | 2026-11-07 | 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 rem | |
CVE-2026-17293 |
high | 8.5 | 0.0035 | 2026-11-07 | 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 rem | |
CVE-2026-17292 |
critical | 9.1 | 0.0040 | 2026-11-07 | 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 rem | |
CVE-2026-17291 |
critical | 9.0 | 0.0053 | 2026-11-07 | 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 rem | |
CVE-2026-17290 |
high | 8.5 | 0.0035 | 2026-11-07 | 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 rem | |
CVE-2026-17289 |
high | 7.7 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17288 |
high | 8.5 | 0.0037 | 2026-11-07 | 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 rem | |
CVE-2026-17287 |
high | 8.5 | 0.0037 | 2026-11-07 | 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 rem | |
CVE-2026-17285 |
high | 7.7 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17284 |
high | 8.5 | 0.0032 | 2026-11-07 | 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 rem | |
CVE-2026-17283 |
high | 7.7 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17282 |
high | 7.7 | 0.0044 | 2026-11-07 | 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 rem | |
CVE-2026-17281 |
high | 7.7 | 0.0044 | 2026-11-07 | 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 rem |