Security alerts · November 9, 2026

IBM API Connect: critical flaws could let attackers run code on the server without logging in

IBM has fixed dozens of flaws in API Connect, several rated CVSS 9.8 to 9.9. The worst could let an attacker run their own code on the server, one of them without logging in. No exploitation has been confirmed yet. The fix is to update to 10.0.8.13 or 12.1.1.3.

What happened

IBM has published two security bulletins for IBM API Connect, a platform used to manage, publish and secure APIs, the interfaces that applications use to talk to each other. The bulletins fix dozens of flaws at once, and the US vulnerability database NVD published entries for the most serious ones on November 7, 2026.

This article focuses on four critical flaws that NVD describes in detail:

  • CVE-2026-17408: input that reaches operating system commands without proper sanitization. According to IBM, a remote attacker could execute arbitrary code.
  • CVE-2026-16720: authentication against a connected directory service is not enforced properly. An attacker could obtain valid access tokens for other users and act under their identity.
  • CVE-2026-17399: uploaded content is not checked properly. A logged-in attacker could get code to run on the server.
  • CVE-2026-16918: a server-side request forgery (SSRF) flaw that could give an attacker access to resources on the internal network.

In the bulletin for the 12.1 branch, IBM also fixes other serious issues, such as hard-coded credentials (CVE-2026-17360) and an authentication bypass via an alternate path (CVE-2026-17313), both rated 9.8. None of the four main flaws is currently listed in the CISA KEV catalog, and the European database EUVD does not report them as exploited either.

Why it is dangerous

The most dangerous is CVE-2026-17408, a so-called OS command injection. Imagine a receptionist who writes a visitor’s name straight into an instruction for the security guard. If the visitor adds another instruction instead of just a name, the guard carries it out without question. The server behaves much the same way with this flaw.

According to IBM’s rating, CVE-2026-17408 and CVE-2026-16720 require no login and no user interaction, and the attack works over the network. CVE-2026-17399 requires the attacker to be logged in, but a low-privilege account is enough. A successful attack could let the attacker run their own code on the server or act as other users. Data the platform manages could also leak. Through SSRF, the attacker could reach resources on the internal network that the server can access.

CVSS is a severity scale from 0 to 10. IBM itself rated these four flaws 9.3 to 9.9 under CVSS 3.1, which is critical, and NVD lists IBM’s scores. The CISA KEV catalog is kept by the US agency CISA and lists flaws with confirmed exploitation. These flaws are not in it yet.

EPSS estimates the probability that a flaw will be exploited in the next 30 days. As of November 8, 2026, it is 0.9% for CVE-2026-17408 and between 0.4% and 0.8% for the other three. That sounds low, but these flaws were only just disclosed and the figure can change quickly.

Who is affected

Affected versions are IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2. This applies to all four flaws described above.

API Connect is mostly used by larger organizations such as banks, insurers, telecoms and public administration that expose their services to partners or mobile apps. It usually runs on Kubernetes or Red Hat OpenShift, or as virtual appliances on VMware. Smaller companies are more likely to encounter it indirectly, through a supplier or integrator who runs the platform for them.

If you do not use API Connect, these flaws do not affect you. IBM does not list other versions in the descriptions of these flaws. If you run an older branch, check with IBM whether it is still supported.

How to check if you are affected

On Kubernetes or OpenShift, the version is shown in the APIConnectCluster object. The following commands only read data and change nothing:

kubectl get apiconnectcluster -A
oc get apiconnectcluster -A

For VMware installations, run apicup version in the project directory to print the version of the installer tool. It usually matches the installed version, and IBM’s documentation explains how to verify each subsystem precisely.

apicup version

If a supplier manages the platform for you, ask them for the exact version number and an update date. Compare it with the list of affected versions.

How to fix it

IBM has released fixed versions: 10.0.8.13 for the 10.0.8 branch and 12.1.1.3 for the 12.1 branch. Recommended steps:

  • List every API Connect installation, including test and standby environments.
  • Start with those whose interfaces are reachable from the internet, then move on to internal ones.
  • Before updating, back up the subsystems as described in IBM’s documentation, especially management and the portal.
  • Read the release notes and the upgrade procedure for your deployment type (Kubernetes, OpenShift, VMware).
  • If possible, try the update in a test environment first.
  • Update to 10.0.8.13 or 12.1.1.3, then confirm the new version with the commands from the previous section.

IBM does not describe a workaround that could replace the update for these flaws. Until you update, restrict access to admin interfaces such as Cloud Manager and API Manager to the internal network or VPN. Review user accounts and remove the ones you do not need. These steps reduce the risk but do not replace the update.

What if you may already be compromised

IBM’s bulletins do not list specific indicators of compromise. If your installation was reachable from the internet, it is worth checking for:

  • new or unknown user accounts, provider organizations and API keys
  • unusual uploads of files or API definitions in the management subsystem logs
  • logins from unusual addresses or at unusual times
  • gateway configuration changes that nobody planned
  • connections from API Connect to internal addresses the server should not reach
  • unknown processes or files in containers or virtual appliances

If you find any of these, first preserve logs and backups as evidence. Then change passwords, tokens and keys, including credentials for the connected directory service. If anything looks suspicious, bring in an incident response specialist or IBM support.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.

See pricing [email protected]