CVE-2026-17301: Plan the two API Connect branch updates separately
IBM rates CVE-2026-17301 Critical with a CVSS 3.1 base score of 9.8. The vulnerability appears in IBM’s November 5, 2026 security bulletins. The IBM CNA record, published on November 7, lists the affected releases and recommended updates.
Select the branch fix
IBM bulletin 7295635 identifies the 12.1 update; bulletin 7295637 identifies the 10.0.8 update. The CNA record confirms both mappings.
| 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. The destination release does not establish a direct upgrade path from every earlier version; confirm the supported procedure and prerequisites for the installed platform.
Group deployments by product branch
Read the full active API Connect product release for each deployment and assign it to the matching row above. Keep the 10.0.8 and 12.1 maintenance plans separate so that each uses its own fixed destination and platform-specific prerequisites.
The two fixes are branch updates, not instructions to migrate between branches. Confirm the supported path from the installed release before scheduling maintenance. Keep operator and platform versions in separate fields; neither identifies the API Connect product branch on its own.
Accept each branch independently
After the supported update completes, verify the running product version and the deployed package or image identity. Check normal service health using the established checks for that environment. Record the result against the same deployment and branch used in the plan.
Success on one branch does not establish completion on the other. Keep any affected deployment open until its own fixed release is verified, and recheck the version if recovery restores an earlier installation. Use the separate results to report which deployments have actually completed maintenance.
Acknowledgements
This post was created with assistance from AI.