CVE-2026-17403: Inventory API Connect releases before patching
IBM rates CVE-2026-17403 Critical with a CVSS 3.1 base score of 9.0. Its CNA record was published on November 7, 2026. The relevant IBM security bulletins were initially published on November 5.
Select the fixed release
IBM bulletin 7295635 identifies the 12.1 branch update; bulletin 7295637 identifies the 10.0.8 branch update. Use the affected ranges in this CVE’s CNA record and the corresponding branch fix.
| Affected API Connect release | Fixed branch release |
|---|---|
| 10.0.8.0 through 10.0.8.12 | 10.0.8.13 |
| 12.1.0.0 through 12.1.1.2 | 12.1.1.3 |
IBM recommends upgrading and lists no workaround in these bulletins. Confirm the supported update path and prerequisites for the current platform. These fixed destinations do not imply that a change between product branches is required or supported.
Record the active release
List every API Connect deployment, its owner, platform and active product release. Include recovery environments and deployments that are currently stopped. Record the version shown by the product’s administrative inventory, then compare it with the deployment system’s package or image record.
Keep the full product version in the change record. A Kubernetes platform version, operator version or downloaded update package does not identify the active API Connect release. If the two inventory sources disagree, resolve that difference before declaring the deployment patched.
Close each inventory entry
After the supported update completes, read the active product version again and record the installed package or image identity. Confirm that normal administrative sign-in and service-health checks pass using an authorized account.
Keep an entry open for any deployment still using an affected release. Update its recovery and provisioning records so that a later restart does not silently restore the old version.
Acknowledgements
This post was created with assistance from AI.