# CVE-2026-18838: IBM API Connect improper authentication and authorization bypass

Source: https://junglewise.ai/threats/cve-2026-18838-ibm-api-connect-12-1-0-0-through-12-1-1-2-could-allow-a-remote  
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-18838 · Severity: critical · CVSS 9.4 · Published 2026-11-07

IBM API Connect is an API management platform that enables organizations to create, manage, and secure APIs. Versions 12.1.0.0 through 12.1.1.2 suffer from multiple critical authentication and authorization flaws that could allow remote attackers to impersonate users, modify API configurations, access sensitive data, and bypass security controls without proper credentials or authentication.

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

## Quick answers

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

**How severe is CVE-2026-18838?** Critical severity, with a CVSS score of 9.4, published 7 November 2026.

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

**Is there a fix for CVE-2026-18838?** Yes: fixed in 12.1.1.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-18838 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-18838?** 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.

## How to fix

- Fixed in 12.1.1.3

## Technical details

The vulnerability encompasses multiple distinct issues: improper identity verification allowing user impersonation (CVE-2026-18838), case sensitivity bypass in access controls (CVE-2026-17409), authentication bypass via alternate paths (CVE-2026-17313), and server-side request forgery (SSRF) issues. These flaws require either no authentication or minimal authentication depending on the specific CVE, are network-accessible, and allow attackers to gain unauthorized administrative access, exfiltrate sensitive information, and modify configurations. IBM addressed these vulnerabilities in version 12.1.1.3.

## Affected products

- IBM API Connect 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)

## 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)