# CVE-2026-75590: IBM API Connect server-side request forgery

Source: https://junglewise.ai/threats/cve-2026-75590-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-75590 · Severity: high · CVSS 7.2 · Published 2026-11-07

IBM API Connect is an API management platform that routes and secures API traffic for enterprises. This vulnerability allows remote attackers to bypass security protections and make the server contact internal network resources, potentially exposing sensitive data from internal systems.

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

## Quick answers

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

**How severe is CVE-2026-75590?** High severity, with a CVSS score of 7.2, 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-75590?** 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-75590 attacked?** It is attacked over the network, in a hosted service.

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

Server-side request forgery (SSRF) in IBM API Connect 12.1.0.0 through 12.1.1.2 allows unauthenticated remote attackers to bypass internal address restrictions and force the server to contact internal services, with responses partially returned to the attacker. The vulnerability exists in the request routing and filtering logic that fails to properly enforce destination restrictions.

## 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 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)
- [IBM API Connect hard-coded cryptographic key in credential storage](https://junglewise.ai/threats/cve-2026-19124-ibm-api-connect-10-0-8-0-through-10-0-8-12-could-allow-an)