CVE-2026-16918: Track API Connect patch completion across deployments
IBM rates CVE-2026-16918 Critical with a CVSS 3.1 base score of 9.3. 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.
Assign completion per deployment
Create a patch entry for each API Connect deployment with its active release, platform and owner. Include standby and disaster-recovery environments where they exist. Group entries by product branch so that each receives the appropriate fixed release.
Use the platform’s documented update order and availability requirements. Do not assume that a sequential restart is supported for every topology, or that one healthy member proves the entire deployment is updated.
Check the whole deployment
After the supported upgrade, confirm the active product version and normal health of every applicable component using the administrative inventory and deployment records. Record pending or failed components separately rather than marking the whole environment complete from the first successful result.
Use ordinary authorized sign-in and read-only health checks to confirm service operation. Update the standby and provisioning records as part of the same change so that an older installation does not return during recovery.
Acknowledgements
This post was created with assistance from AI.