# CVE-2026-17428: IBM API Connect authorization bypass in request URL parameters

Source: https://junglewise.ai/threats/cve-2026-17428-ibm-api-connect-10-0-8-0-through-10-0-8-12-and-12-1-0-0-through  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-07. Updated: 2026-11-07  
License: CC BY 4.0 with a link back

CVE-2026-17428 · Severity: medium · CVSS 5 · Published 2026-11-07

IBM API Connect is an enterprise platform for creating and managing APIs. A flaw in how the system validates permissions allows authenticated users to access sensitive information belonging to other organizations or accounts by manipulating values in request URLs. An attacker with valid credentials could view confidential data without proper authorization checks.

Technologies: [IBM API Connect](https://junglewise.ai/threats/technologies/api-connect). Vendors: [IBM](https://junglewise.ai/threats/vendors/ibm).

## Quick answers

**Is CVE-2026-17428 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-17428 being exploited in the wild.

**How severe is CVE-2026-17428?** Medium severity, with a CVSS score of 5, published 7 November 2026.

**Which products and versions are affected?** IBM API Connect 10.0.8.0 through 10.0.8.12; 12.1.0.0 through 12.1.1.2.

**Is there a fix for CVE-2026-17428?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-17428 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-17428?** Check whether you run IBM API Connect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an authorization bypass (CWE-639) caused by insufficient verification of user-supplied URL parameters used in access control decisions. An authenticated attacker can craft requests with modified URL values to bypass authorization checks and access resources belonging to other users or tenants. The flaw affects versions 10.0.8.0–10.0.8.12 and 12.1.0.0–12.1.1.2.

## Affected products

- IBM API Connect 10.0.8.0 through 10.0.8.12; 12.1.0.0 through 12.1.1.2

## Timeline

- 2026-11-07: disclosed

## References

- [https://www.ibm.com/support/pages/node/7295635](https://www.ibm.com/support/pages/node/7295635)
- [https://www.ibm.com/support/pages/node/7295637](https://www.ibm.com/support/pages/node/7295637)

## Related threats

- [IBM API Connect server-side request forgery](https://junglewise.ai/threats/cve-2026-75590-ibm-api-connect-12-1-0-0-through-12-1-1-2-could-allow-a-remote)
- [IBM API Connect missing authorization in index access](https://junglewise.ai/threats/cve-2026-19131-ibm-api-connect-12-1-0-0-through-12-1-1-2-could-allow-low)
- [IBM API Connect improper backup server certificate verification](https://junglewise.ai/threats/cve-2026-19129-ibm-api-connect-10-0-8-0-through-10-0-8-12-and-12-1-0-0-through)
- [IBM API Connect server-side request forgery via unauthorized request](https://junglewise.ai/threats/cve-2026-19128-ibm-api-connect-12-1-0-0-through-12-1-1-2-could-allow-an)
- [IBM API Connect weak cryptographic algorithms in authentication](https://junglewise.ai/threats/cve-2026-19126-ibm-api-connect-10-0-8-0-through-10-0-8-12-and-12-1-0-0-through)