API CONNECT · CVE-2026-16718 · Infrastructure
FIX → 10.0.8.13 · 12.1.1.3 ✓ verified
IBM API Connect 10.0.8.0-10.0.8.12 and 12.1.0.0-12.1.1.2 do not properly validate file paths (CWE-22). A remote authenticated attacker can read sensitive information. IBM fixed it in 10.0.8.13 and 12.1.1.3; no workaround is listed.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running self-managed IBM API Connect 10.0.8.0-10.0.8.12 or 12.1.0.0-12.1.1.2 where users can hold valid accounts: any such account can exploit improper file path validation (path traversal) to read sensitive information. IBM does not name the endpoint or a required setting. Instances already on 10.0.8.13 or 12.1.1.3 can skip it.
Not affected if unaffected-version, versions-outside-affected-ranges
Who cares api-gateway, ibm-api-connect, self-hosted
10.0.8.0 to 10.0.8.12 and 12.1.0.0 to 12.1.1.210.0.8.13 and 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 remote authenticated attacker to obtain sensitive information due to improper validation of file paths.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
12.1.1.3Upgrade to 10.0.8.13 · 12.1.1.3
10.0.8.x to 10.0.8.13, or 12.1.x to 12.1.1.3, via IBM Fix Central