Browse All CVEs
50,445 vulnerabilities.
| CVE | Severity | CVSS | EPSS | First Seen | Flags | Description |
|---|---|---|---|---|---|---|
CVE-2026-17280 |
critical | 9.1 | 0.0057 | 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-17279 |
medium | 6.5 | 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-17278 |
high | 7.5 | 0.0066 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to gain unauthoriz | |
CVE-2026-17244 |
high | 7.4 | 0.0033 | 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-17241 |
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-17240 |
medium | 5.3 | 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-17239 |
high | 8.8 | 0.0085 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to e | |
CVE-2026-17238 |
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-17237 |
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-17236 |
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-17233 |
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-17232 |
medium | 6.1 | 0.0031 | 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-17231 |
medium | 5.8 | 0.0042 | 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-17230 |
medium | 5.4 | 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-17228 |
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-17225 |
medium | 5.4 | 0.0034 | 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-17215 |
medium | 4.3 | 0.0038 | 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-17214 |
medium | 4.8 | 0.0034 | 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-17211 |
medium | 4.3 | 0.0046 | 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-17202 |
medium | 5.3 | 0.0040 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to enumerate usern | |
CVE-2026-17190 |
high | 8.7 | 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-17188 |
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-17187 |
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-17172 |
high | 8.5 | 0.0056 | 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-17167 |
medium | 4.3 | 0.0034 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to f | |
CVE-2026-17158 |
critical | 9.9 | 0.0066 | 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-17155 |
medium | 5.4 | 0.0032 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to e | |
CVE-2026-17154 |
medium | 5.4 | 0.0027 | 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-17150 |
critical | 9.9 | 0.0080 | 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-17147 |
high | 8.8 | 0.0095 | 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-17146 |
critical | 9.9 | 0.0067 | 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-17144 |
medium | 4.3 | 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-17143 |
medium | 4.3 | 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-17140 |
high | 8.8 | 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-17139 |
medium | 5.4 | 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-17137 |
medium | 5.5 | 0.0009 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a local attacker to obtain sensitive | |
CVE-2026-17134 |
high | 8.8 | 0.0052 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to e | |
CVE-2026-17132 |
high | 8.8 | 0.0063 | 2026-11-07 | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to e | |
CVE-2026-17131 |
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-17129 |
high | 8.1 | 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-17128 |
medium | 6.5 | 0.0048 | 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-17117 |
high | 8.8 | 0.0082 | 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-17114 |
high | 8.1 | 0.0052 | 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-17112 |
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-17108 |
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-17098 |
medium | 5.3 | 0.0042 | 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-17085 |
medium | 4.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-17067 |
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-17066 |
critical | 9.1 | 0.0056 | 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-17064 |
medium | 5.0 | 0.0034 | 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 |