CVE-2026-19131 · Vendor
NO FIX YET
IBM API Connect 12.1.0.0 through 12.1.1.2 is missing an authorization check, so a low-privileged user can query arbitrary indices. An attacker with a basic account can read sensitive data they should not see.
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 where some users hold low-privileged accounts. The sources do not say which deployment or configuration is needed to reach the query path. unknown whether managed or default setups are affected.
Not affected if outside-affected-range
Who cares api-gateway, ibm-api-connect, self-hosted
No fix yet, per the sources.
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow low-privileged users to query arbitrary indices and read sensitive data due to missing authorization.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.