CVE-2026-17167 · Infrastructure
NO FIX YET
IBM API Connect versions 12.1.0.0 through 12.1.1.2 trust client-supplied data when recording the source of a request. An authenticated remote attacker can therefore write inaccurate source details into audit records.
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 users can send authenticated requests to the gateway or management APIs. The flaw affects audit record integrity, not direct code execution or data access. Deployments on other versions are not in the stated range.
Not affected if outside-affected-versions
Who cares api-gateway, audit-logging, ibm-api-connect
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 authenticated attacker to falsify audit log information due to reliance on untrusted inputs. Information supplied by the client is relied on when recording the source of a request, so audit records could contain inaccurate details.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.