Export limit exceeded: 421027 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (421027 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-17321 | 1 Ibm | 1 Api Connect | 2026-11-07 | 8.1 High |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to delete or overwrite arbitrary control-plane assets due to an insecure direct object reference. | ||||
| CVE-2026-17320 | 1 Ibm | 1 Api Connect | 2026-11-07 | 7.7 High |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to an insecure direct object reference. | ||||
| CVE-2026-17319 | 1 Ibm | 1 Api Connect | 2026-11-07 | 7.1 High |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to modify tool configuration and cause a denial of service due to improper authorization. Information supplied by the client is relied on when deciding what a user is allowed to do, which could allow unauthorized changes that disrupt service. | ||||
| CVE-2026-17318 | 1 Ibm | 1 Api Connect | 2026-11-07 | 7.7 High |
| 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 attacker to obtain sensitive information due to improper authorization. | ||||
| CVE-2026-17317 | 1 Ibm | 1 Api Connect | 2026-11-07 | 6.4 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to access internal resources and cause a denial of service due to server-side request forgery. | ||||
| CVE-2026-17316 | 1 Ibm | 1 Api Connect | 2026-11-07 | 7.2 High |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to perform server-side request forgery due to improper validation of user-supplied input. | ||||
| CVE-2026-17315 | 1 Ibm | 1 Api Connect | 2026-11-07 | 5.8 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to improper validation of user-supplied URLs. | ||||
| CVE-2026-17314 | 1 Ibm | 1 Api Connect | 2026-11-07 | 5 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery. | ||||
| CVE-2026-17313 | 1 Ibm | 1 Api Connect | 2026-11-07 | 9.8 Critical |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and take control of gateway configuration due to authentication bypass via an alternate path. | ||||
| CVE-2026-17312 | 1 Ibm | 1 Api Connect | 2026-11-07 | 5.4 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to force a user to authenticate into an attacker-controlled account due to cross-site request forgery. The sign-in flow does not sufficiently verify that a login response belongs to the user's own request, which could link the victim's session to an account controlled by the attacker. | ||||
| CVE-2026-17311 | 1 Ibm | 1 Api Connect | 2026-11-07 | 7.1 High |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to modify application API subscriptions due to broken object-level authorization. | ||||
| CVE-2026-17310 | 1 Ibm | 1 Api Connect | 2026-11-07 | 6.5 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to the use of a hard-coded cryptographic key. | ||||
| CVE-2026-17309 | 1 Ibm | 1 Api Connect | 2026-11-07 | 8 High |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and tamper with configuration due to improper certificate validation. | ||||
| CVE-2026-17308 | 1 Ibm | 1 Api Connect | 2026-11-07 | 6.8 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive credentials and manipulate tool responses due to improper certificate validation. | ||||
| CVE-2026-17307 | 1 Ibm | 1 Api Connect | 2026-11-07 | 6.5 Medium |
| 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 attacker to obtain sensitive information due to broken object-level authorization. | ||||
| CVE-2026-17306 | 1 Ibm | 1 Api Connect | 2026-11-07 | 5.8 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information from internal network resources due to server-side request forgery. | ||||
| CVE-2026-17305 | 1 Ibm | 1 Api Connect | 2026-11-07 | 5.5 Medium |
| 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 attacker to obtain sensitive information due to server-side request forgery. | ||||
| CVE-2026-17304 | 1 Ibm | 1 Api Connect | 2026-11-07 | 6.4 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper input validation. Locations supplied when service definitions are imported are not sufficiently validated, which could allow the server to retrieve content it should not access. | ||||
| CVE-2026-17303 | 1 Ibm | 1 Api Connect | 2026-11-07 | 6.4 Medium |
| 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 attacker to access internal network resources due to improper validation of a user-supplied URL. The address is not sufficiently restricted, which could allow the server to contact internal systems. | ||||
| CVE-2026-17302 | 1 Ibm | 1 Api Connect | 2026-11-07 | 5 Medium |
| IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to probe internal network services due to improper validation of a user-supplied URL. | ||||