# CVE-2026-19129: IBM API Connect improper backup server certificate verification

Source: 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  
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-19129 · Severity: medium · CVSS 6.8 · Published 2026-11-07

IBM API Connect is a platform for managing and publishing APIs. An attacker positioned on the network can intercept backup data sent to analytics servers because the backup server's identity is not properly verified, potentially exposing sensitive configuration and credentials.

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

## Quick answers

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

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

**Am I affected by CVE-2026-19129?** 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 improper certificate validation (CWE-295) in the analytics backup mechanism. When API Connect establishes a secure connection to backup servers, it fails to verify the backup server's identity, allowing network-positioned attackers to perform man-in-the-middle attacks. Backup data and embedded credentials can be intercepted without authentication required from the attacker.

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