CVE-2026-1501
IBM Concert 1.0 through 3.0.0 is vulnerable to Improper Certificate Validation.
CVSS
3.7
Baixa
EPSS
0.1%
p0
KEV
—
Exploit Today
0
0-100
Publicado: 19 de out. de 2026 · Última mod.: 3 de nov. de 2026 · CWE-295
0.1%EPSS · 30 dias0.1%
2026-10-202026-11-06
IBM Concert 1.0 through 3.0.0 is vulnerable to Improper Certificate Validation.
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-191296.8 MÉD—
———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 network-positioned attacker to intercept backup data due to improper verification of the backup server's identity. The identity of the backup server is not verified when the secure connection for analytics backups is established, which could allow backup data, and credentials if used, to be intercepted.14hCVE-2026-173338.0 ALT—
———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 bypass authentication and inject unauthorized configuration changes due to improper certificate validation.14hCVE-2026-173328.7 ALT—
———IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to bypass security restrictions due to improper certificate validation.14hCVE-2026-173098.0 ALT—
———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.14hCVE-2026-173086.8 MÉD—
———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.14hCVE-2026-48057——
———Botan is a C++ cryptography library. Prior to 3.13.0, Botan's X.509 Distinguished Name decoder flattens the Attribute-Value Assertions in each Relative Distinguished Name and loses multi-value RDN grouping before DN name-constraint enforcement. An attacker controlling a name-constrained intermediate CA can issue a certificate with a multi-value RDN whose first Common Name matches the permitted constraint and whose second Common Name is attacker-chosen, causing the constraint check to accept the flattened first value. If the certificate contains no subjectAlternativeName extension, the second Common Name can then be accepted as a hostname; Botan does not fall back to Common Name hostname matching when any subjectAlternativeName is present. The exposure is limited to deployments using DN name constraints, which are uncommon outside internal PKIs, and to certificates without a subjectAlternativeName. This issue is fixed in version 3.13.0.21h