CVE-2026-17310 · Infrastructure
NO FIX YET
IBM API Connect versions 12.1.0.0 through 12.1.1.2 ship with a hard-coded cryptographic key. A remote attacker can use that key to obtain sensitive information.
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 12.1.0.0 through 12.1.1.2 are in scope. The sources do not say which deployment configurations or data paths are exposed, so check the IBM security bulletin for details.
Not affected if unknown
Who cares ibm-api-connect, self-hosted
12.1.0.0 through 12.1.1.2No fix yet, per the sources.
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to the use of a hard-coded cryptographic key.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.