# CVE-2026-19128: IBM API Connect server-side request forgery via unauthorized request

Source: https://junglewise.ai/threats/cve-2026-19128-ibm-api-connect-12-1-0-0-through-12-1-1-2-could-allow-an  
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-19128 · Severity: high · CVSS 7.5 · Published 2026-11-07

IBM API Connect is an API management platform that handles API traffic and security. An authenticated attacker can exploit a server-side request forgery vulnerability to send unauthorized requests from the system, allowing them to enumerate internal network resources or probe other systems as a stepping stone for further attacks.

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

## Quick answers

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

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

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

CVE-2026-19128 is a server-side request forgery (CWE-918) in IBM API Connect versions 12.1.0.0 through 12.1.1.2 that requires an authenticated attacker to exploit. By manipulating request parameters, an attacker can cause the API Connect server to make outbound requests to internal or external network resources, potentially revealing sensitive information about the network topology or enabling reconnaissance.

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