API-CONNECT · CVE-2026-16918 · Vendor
FIX → 12.1.1.3 · 10.0.8.13
IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 contains a server-side request forgery flaw. A remote attacker can make the server send requests into the internal network and reach resources that should be private.
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. IBM rates it 9.3 with network access and no login needed, so an outside attacker can make the server send requests to internal network resources. No special setting is named; the bulletin does not say which endpoint is involved. Anyone already on 10.0.8.13 or 12.1.1.3 can skip it.
Who cares api-gateway, ibm-api-connect, self-hosted
10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.210.0.8.13 and 12.1.1.3IBM 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 attacker to access internal network resources due to server-side request forgery.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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.
Upgrade to 12.1.1.3 · 10.0.8.13
10.0.8.13 (10.0.8.x line) or v12.1.1.3 (12.1.x line); IBM Fix Central12.1.1.3 link: https://www.ibm.com/support/pages/node/7290205