Cyber & AI intelligence
Briefs indexed3824
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-17333 2026-11-18

CVE-2026-17333: IBM API Connect Authentication Bypass via Improper Certificate Validation

"IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 have a certificate validation flaw that could let a remote attacker bypass authentication and inject unauthorized configuration changes."

IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 have a certificate validation flaw that could let a remote attacker bypass authentication and inject unauthorized configuration changes.

What Is It

CVE-2026-17333 is an improper certificate validation weakness (CWE-295) in IBM API Connect. According to the NVD record, IBM's PSIRT reported it. A remote attacker could exploit it to bypass authentication and push unauthorized configuration changes to the affected product. NVD published the record on 2026-11-07 and last modified it on 2026-11-18. Its status is "Analyzed."

Why It Matters

The record carries two different CVSS v3.1 scores:

Both scores rate confidentiality and integrity impact as High and availability impact as None. An attacker who can change configuration on an API management platform without authenticating could affect the APIs it fronts.

As of the NVD record's last modification on 2026-11-18, it does not show this CVE in CISA's Known Exploited Vulnerabilities catalog. CISA's SSVC assessment in the CVE record, dated 2026-11-09, lists exploitation as "none," automatable as "no" and technical impact as "total." Neither the NVD record nor the CVE record reports any active exploitation.

What's Vulnerable

The affected product is IBM API Connect:

NVD's configuration data matches these versions as vulnerable:

Patch Status

IBM has published two vendor advisories for this issue (linked below). NVD's version ranges stop at 10.0.8.13 and 12.1.1.3, so versions from those onward are not listed as vulnerable. Administrators should check the IBM advisories for the exact fixed releases and remediation steps, then upgrade affected deployments. Because NVD does not list this CVE as being in KEV, there is no CISA-mandated required action or due date.

Sources