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