Enterprise-grade API management (IBM API Connect) affected; auth bypass can expose APIs/configs across many organizations; widely used in large enterprises.
CVE-2026-17326
Authentication bypass in IBM API Connect allowing access control bypass
Is CVE-2026-17326 being exploited?
Not confirmed. CVE-2026-17326 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-17326?
CVE-2026-17326 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-17326?
Not known from our data. No patch reference has been recorded for CVE-2026-17326, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-17326 affect?
CVE-2026-17326 affects IBM API Connect 10.0.8.0 - 10.0.8.12, IBM API Connect 12.1.0.0 - 12.1.1.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17326?
Apply vendor fixes/mitigations ASAP; restrict admin access and audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated remote attacker can bypass access controls to read/modify APIs, configs, and data, and potentially escalate privileges.
Patch when possible
- affected>= 12.1.0.0 and <= 12.1.1.2
- affected>= 10.0.8.0 and <= 10.0.8.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
timeline
- 7 Nov 2026Published
- 7 Nov 2026CVE record last updated · same day later
- 8 Nov 2026Analysed by vulneraibility.com · 1 day later
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.