cve.bz

CVE-2026-17333 ibm api connect: Improper Certificate Validation

8.0 highEPSS 0.2%

High (8.0) in ibm api connect. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-17333 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-17333?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-17333?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-17333 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-17333

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-17333](https://cve.bz/cve/badge/CVE-2026-17333.svg)](https://cve.bz/cve/CVE-2026-17333)

HTML:

<a href="https://cve.bz/cve/CVE-2026-17333"><img src="https://cve.bz/cve/badge/CVE-2026-17333.svg" alt="CVE-2026-17333"></a>

Affected

  • ibm:api connect

Versions

From the CNA's record in the CVE List.

ProductAffected
IBM API Connectfrom 12.1.0.0 through 12.1.1.2
IBM API Connectfrom 10.0.8.0 through 10.0.8.12

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON