Skip to content
CVE-2026-17399: Keep replacement API Connect instances on the fixed release

CVE-2026-17399: Keep replacement API Connect instances on the fixed release

November 19, 2026

IBM rates CVE-2026-17399 Critical with a CVSS 3.1 base score of 9.9. Its IBM CNA record, published on November 7, 2026, lists the affected releases and recommended updates. The relevant IBM bulletins were initially published on November 5.

Choose the supported branch update

IBM bulletin 7295635 covers the 12.1 branch; bulletin 7295637 covers 10.0.8. The CNA record gives these affected ranges and fixed destinations.

Affected API Connect releaseFixed branch release
10.0.8.0 through 10.0.8.1210.0.8.13
12.1.0.0 through 12.1.1.212.1.1.3

IBM recommends upgrading. Confirm the supported path and prerequisites for the installed platform before applying the corresponding branch update.

Include replacement instances in the update

Identify the deployment definition used to create a replacement API Connect instance. Record its selected package or image alongside the running product release. Updating a live instance while leaving the old deployment definition in place can allow a later replacement to restore an affected release.

Use the supported update procedure and retain the exact package or image identity in the change record. If the platform uses a separately versioned operator, record that version separately; it does not substitute for the API Connect product version.

Confirm the reusable deployment definition

After the rollout, read the active product release from administrative inventory and compare it with the deployment definition. Check that the definition retained for subsequent provisioning selects the intended fixed release and meets IBM’s prerequisites.

Use normal service-health checks to accept the rollout. If a replacement instance is created as part of the approved maintenance procedure, verify its active product release as well. Do not create extra instances solely to reproduce the vulnerability. Close the change only after the running deployment and its provisioning record agree.

Acknowledgements

This post was created with assistance from AI.

Last updated on