Skip to content
IBM API Connect: November 2026 patch matrix for 29 Critical CVEs

IBM API Connect: November 2026 patch matrix for 29 Critical CVEs

November 19, 2026

IBM’s November 5, 2026 security bulletins identify the branch updates for the 29 Critical vulnerabilities listed here. Bulletin 7295635 covers the 12.1 branch, and bulletin 7295637 covers 10.0.8. The linked IBM-authored CNA records were published on November 7; that later record date is separate from the bulletin disclosure.

All scores below are IBM CVSS 3.1 base scores. Match each CVE to its branch group before selecting an update. A branch whose scope is not established in a group must not be treated as unaffected.

CVEs confirmed on both branches

For each of these 15 CVEs, the affected and fixed releases are:

Affected API Connect release, inclusiveFixed 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
CVE and IBM CNA recordIBM CVSS 3.1 score
CVE-2026-171179.9
CVE-2026-171509.9
CVE-2026-172929.1
CVE-2026-172969.6
CVE-2026-172979.6
CVE-2026-172989.9
CVE-2026-173429.9
CVE-2026-173599.9
CVE-2026-173929.9
CVE-2026-173969.6
CVE-2026-174029.9
CVE-2026-174089.8
CVE-2026-174099.4
CVE-2026-174109.9
CVE-2026-188369.3

CVEs with confirmed 12.1 scope

For each of these 14 CVEs, IBM identifies 12.1.0.0 through 12.1.1.2, inclusive, as affected and 12.1.1.3 as the fixed branch release. These rows do not establish 10.0.8 applicability. Do not copy the dual-branch mapping from another CVE in the same bulletin.

CVE and IBM CNA recordIBM CVSS 3.1 score
CVE-2026-168849.9
CVE-2026-169209.9
CVE-2026-170499.9
CVE-2026-170669.1
CVE-2026-171329.9
CVE-2026-171349.9
CVE-2026-172789.8
CVE-2026-173409.8
CVE-2026-173449.3
CVE-2026-173539.6
CVE-2026-173549.9
CVE-2026-173609.8
CVE-2026-173629.8
CVE-2026-188389.4

Apply and verify the appropriate update

Record the full active API Connect product version, deployment identity and platform for each installation. Include standby and recovery deployments. Keep product, operator and platform versions separate so that the branch decision uses the product release.

Select the matching fixed destination and follow IBM’s supported procedure for the actual starting release and platform. The fixed-release number alone does not establish a direct upgrade path from every earlier version or authorize a branch migration. Check prerequisites, backup requirements and any required restart or replacement steps before the maintenance window.

After the update completes, read the active product version again and reconcile it with the deployed package or image identity. Check ordinary service health and administrative access using an authorized account. A downloaded package, an updated template or a successful check on one instance does not establish that every applicable component is running the fix.

Record the final version and check results per deployment. Keep incomplete installations open, and update the provisioning and recovery records so that a later replacement does not restore an affected release. If recovery does restore one, reassess its patch status before closing the change.

The workflow verifies normal operation and installed-release evidence. It does not reproduce the vulnerabilities or substitute operational health checks for the required update.

Acknowledgements

This post was created with assistance from AI.

Last updated on