NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
CRITICAL severity

CVE-2026-16720 — Ibm Api Connect

CRITICAL

CVE-2026-16720 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in ibm api connect. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain valid access tokens for other users due to improper authentication.…

Published
Updated
Affected
1 product
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Description

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain valid access tokens for other users due to improper authentication. Authentication against a connected directory service is not sufficiently enforced, which could allow another user's identity to be assumed.

Affected Products

1 product · 4 configurations
Application
api connectibm
4 versions
10.0.8.010.0.8.1212.1.0.012.1.1.2

Detection & mitigation playbook

Vendor / appliance

  1. Detect

    Inventory every ibm api connect deployment and check each version against the affected-products list above.

  2. Remediation status

    The records we use list no fixed version for CVE-2026-16720. Check the ibm api connect advisory for a patched release, and apply the workarounds below until you can upgrade.

  3. Mitigate without a patch

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain valid access tokens for other users due to improper authentication. Authentication against a connected directory service is not sufficiently enforced, which could allow another user's identity to be assumed.
O3 Security · Runtime Protection

Is CVE-2026-16720 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works