API CONNECT V12 ONPREM · CVE-2026-18535 · Vendor
FIX → 12.1.1.3
IBM says the API Connect Analytics component (analytics-v2-director) in the v10.0.8 release stream is vulnerable to ReDoS and to improper neutralisation of wildcard query operators (CWE-1333, IBM CVSS 9.6, PR:L, network). IBM's bulletin lists the affected product as API Connect V12 OnPrem v12.1.0.0 - v12.1.1.2, fixed in v12.1.1.3. The description and the bulletin disagree on stream (v10.0.8 vs v12.1), so treat both as potentially affected. No workaround.
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 (on-prem) IBM API Connect with the Analytics subsystem, V12 v12.1.0.0 - v12.1.1.2 per IBM's bulletin. The flaw needs a low-privileged authenticated network user (PR:L). The 10.0.8 stream is named in the CVE description but the bulletin does not confirm it or give a fix. Others can skip it.
Not affected if unaffected-version, v12.1.1.3-or-later
Who cares analytics, api-gateway, ibm-api-connect, self-hosted
v12.1.0.0 - v12.1.1.2 as affected10.0.8.0 - 10.0.8.12, but IBM's 10.0.8.13 bulletin does not list this CVE, so confirm with IBM supportIBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 are vulnerable to a Regular Expression Denial of Service (ReDoS) attack and to improper neutralisation of wildcard query operators.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H
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
v12.1.1.3 (IBM bulletin; Fix Central https://www.ibm.com/support/pages/node/7290205)10.0.8 stream no fixed version is named in the bulletin that lists this CVE; IBM's 10.0.8.13 bulletin does not list CVE-2026-18535