CVE-2026-19129 · Infrastructure
NO FIX YET
IBM API Connect does not verify the identity of the backup server when it sets up a secure connection for analytics backups. A network-positioned attacker can impersonate that server and intercept backup data, and any credentials sent with it.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running IBM API Connect 10.0.8.x up to 10.0.8.12 or 12.1.x up to 12.1.1.2 that use analytics backups. The risk is an attacker on the network path between API Connect and the backup server. Deployments on other versions, or without analytics backups, are not described as affected.
Not affected if no-analytics-backups, other-versions
Who cares api-gateway, ibm-api-connect, self-hosted
No fix yet, per the sources.
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 network-positioned attacker to intercept backup data due to improper verification of the backup server's identity. The identity of the backup server is not verified when the secure connection for analytics backups is established, which could allow backup data, and credentials if used, to be intercepted.
This page as .md · .json · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.