# CVE-2026-19124: IBM API Connect hard-coded cryptographic key in credential storage

Source: https://junglewise.ai/threats/cve-2026-19124-ibm-api-connect-10-0-8-0-through-10-0-8-12-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-19124 · Severity: medium · CVSS 6.8 · Published 2026-11-07

IBM API Connect is a platform that manages APIs and integration for enterprise applications. Versions 10.0.8.0 through 10.0.8.12 use a hard-coded encryption key to protect stored credentials, allowing an attacker who gains access to the database to decrypt and steal sensitive credentials like API keys and passwords.

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

## Quick answers

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

**How severe is CVE-2026-19124?** 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.

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

**How is CVE-2026-19124 attacked?** It is attacked with local access, in a hosted service.

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

## Technical details

The vulnerability stems from the use of a hard-coded cryptographic key embedded in the product to encrypt stored credentials. An attacker with access to the stored data (e.g., via database breach or compromised backup) can leverage the built-in key to decrypt sensitive credentials without authentication. This is a weak cryptographic practice that violates secure credential storage principles.

## Affected products

- IBM API Connect 10.0.8.0 through 10.0.8.12

## Timeline

- 2026-11-07: disclosed

## References

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