On November 7, 2026, NVD published 35 IBM API Connect CVEs in a single drop. IBM rates every one of them CRITICAL, between 9.0 and 9.9. This isn't one bug — it reads like a full platform audit made public in one go, with nearly every family of web vulnerability represented.
Two branches are affected:
- 12.1.0.0 through 12.1.1.2: all 35 CVEs;
- 10.0.8.0 through 10.0.8.12: 17 of them.
Fourteen require no authentication at all, including two sets of hard-coded credentials that, according to IBM, grant full administrative control.
The Short Version
| Item | Detail |
|---|---|
| Product | IBM API Connect (API management: manager, developer portal, gateway) |
| NVD publication | 2026-11-07 |
| Scores | CVSS 3.1 published by IBM (CNA) |
| NVD status | Undergoing Analysis or Awaiting Analysis: no NVD score, no CPE configuration |
| Unauthenticated | 14 CVEs (PR:N) |
| Account required | 20 CVEs (PR:L), 1 CVE (PR:H) |
| IBM bulletins | support page 7295635 (all CVEs), page 7295637 (cited for those that also hit 10.0.8) |
| CISA KEV | no |
Affected versions come from the NVD descriptions, since NVD hasn't published a CPE configuration yet. No fixed version appears there: you'll find it in IBM's bulletins.
The 14 CVEs Exploitable Without an Account
Start here, especially if the manager or the portal is reachable from the internet.
| CVE | Nature (CWE) | CVSS 3.1 (IBM) | Branches |
|---|---|---|---|
| CVE-2026-17360 | Hard-coded credentials (CWE-798): full administrative control | 9.8 | 12.1 |
| CVE-2026-17403 | Hard-coded credentials (CWE-798): full administrative control | 9.0 | 10.0.8, 12.1 |
| CVE-2026-17301 | Improper cryptographic signature verification (CWE-347): authentication bypass | 9.8 | 10.0.8, 12.1 |
| CVE-2026-16720 | Authentication against the connected directory not enforced (CWE-287): other users' access tokens | 9.8 | 10.0.8, 12.1 |
| CVE-2026-17313 | Authentication bypass via alternate path (CWE-288): control of gateway configuration | 9.8 | 12.1 |
| CVE-2026-17278 | Improper authentication (CWE-290): access to API catalog and runtime configuration | 9.8 | 12.1 |
| CVE-2026-18838 | Identity in requests not verified (CWE-290): impersonation of another user | 9.4 | 12.1 |
| CVE-2026-16884 | XML external entity injection (CWE-611) | 9.9 | 12.1 |
| CVE-2026-17297 | Open redirect at sign-in (CWE-601): account takeover | 9.6 | 10.0.8, 12.1 |
| CVE-2026-17344 | SSRF in a service reachable without authentication (CWE-918) | 9.3 | 12.1 |
| CVE-2026-17131 | SSRF, outbound restrictions bypassed (CWE-918) | 9.3 | 12.1 |
| CVE-2026-17329 | Improper validation of endpoint URLs (CWE-918) | 9.3 | 12.1 |
| CVE-2026-16918 | SSRF to internal network resources (CWE-918) | 9.3 | 10.0.8, 12.1 |
| CVE-2026-18836 | SSRF with the response returned to the attacker (CWE-918) | 9.3 | 10.0.8, 12.1 |
CVE-2026-17297 needs the victim to interact (UI:R): per the description, the redirect address used during sign-in isn't validated well enough, so authentication results can be sent to an attacker-controlled location. CVE-2026-17403 carries high attack complexity (AC:H); IBM doesn't spell out the condition.
The hard-coded credentials
Two CVEs (CVE-2026-17360 and CVE-2026-17403) fall under CWE-798. The NVD descriptions don't say which component is involved or what kind of credentials they are. By definition, hard-coded credentials are the same from one installation to the next, and IBM says they grant full administrative control. As a rule, this class of flaw isn't something you fix by changing a password in the UI — plan on the fixed release.
Five unauthenticated SSRFs
An API management platform exists to call backend services, so it usually sits with broad reach into the internal network. An SSRF in that kind of component can reach whatever the gateway reaches: internal services, admin interfaces, cloud metadata. That's an inference from the product's role — the descriptions themselves talk about requests to "unintended destinations" and, for CVE-2026-16918, "internal network resources".
The 21 CVEs That Need an Account
An API Connect account isn't necessarily an admin: developer portals routinely hand out accounts to partners and external developers. And several of these flaws explicitly cross the boundary between tenants or organizations.
| CVE | Nature (CWE) | CVSS 3.1 (IBM) | Branches |
|---|---|---|---|
| CVE-2026-17402 | OS command injection (CWE-78): commands on the host | 9.9 | 10.0.8, 12.1 |
| CVE-2026-17354 | Path traversal (CWE-22): arbitrary file writes | 9.9 | 12.1 |
| CVE-2026-17336 | SQL injection (CWE-89) | 9.9 | 12.1 |
| CVE-2026-17134 | SQL injection (CWE-89) | 9.9 | 12.1 |
| CVE-2026-17132 | SQL injection (CWE-89) | 9.9 | 12.1 |
| CVE-2026-17396 | SQL injection (CWE-89): information disclosure | 9.6 | 10.0.8, 12.1 |
| CVE-2026-17392 | LDAP injection (CWE-90): admin access to other tenants | 9.9 | 10.0.8, 12.1 |
| CVE-2026-17410 | Argument delimiters not neutralized (CWE-88): other tenants' portal data | 9.9 | 10.0.8, 12.1 |
| CVE-2026-17158 | Improper authentication (CWE-287): privilege escalation | 9.9 | 10.0.8, 12.1 |
| CVE-2026-17146 | Arbitrary JavaScript execution (CWE-79) | 9.9 | 10.0.8, 12.1 |
| CVE-2026-17049 | Authorization bypass through user-controlled key (CWE-639) | 9.9 | 12.1 |
| CVE-2026-16920 | Confused deputy (CWE-441) | 9.9 | 12.1 |
| CVE-2026-17298 | SSRF (CWE-918) | 9.9 | 10.0.8, 12.1 |
| CVE-2026-17299 | Unrestricted resolution of external references (CWE-918): file reads and SSRF | 9.6 | 10.0.8, 12.1 |
| CVE-2026-17296 | SSRF (CWE-918) | 9.6 | 10.0.8, 12.1 |
| CVE-2026-17353 | SSRF (CWE-918): security restriction bypass | 9.6 | 12.1 |
| CVE-2026-17394 | Improperly controlled modification of object attributes (CWE-915) | 9.6 | 10.0.8, 12.1 |
| CVE-2026-17339 | Path traversal (CWE-22): other tenants' resources | 9.1 | 12.1 |
| CVE-2026-17338 | Broken object-level authorization (CWE-639) | 9.1 | 12.1 |
| CVE-2026-17292 | Broken object-level authorization (CWE-639): taking ownership of other organizations | 9.1 | 10.0.8, 12.1 |
| CVE-2026-17066 | Missing authorization (CWE-862): other tenants' data, high privileges required | 9.1 | 12.1 |
What most of these scores share is S:C (scope changed): IBM considers the impact extends beyond the attacked component, which matches descriptions that mention other tenants, other organizations or the underlying host.
CVE-2026-17299 deserves a note: per its description, externally referenced content in submitted definitions isn't sufficiently restricted. On an API platform, submitting a definition is just what developers do all day.
Affected Versions
| Branch | Affected versions (NVD descriptions) | CVEs |
|---|---|---|
| 12.1 | 12.1.0.0 through 12.1.1.2 | all 35 |
| 10.0.8 | 10.0.8.0 through 10.0.8.12 | 17 (marked "10.0.8" above) |
⚠️ These are bounds taken from the descriptions, not the version to install. NVD lists no fixed version for any of these CVEs. The release to deploy on each branch is in IBM's bulletins (support pages 7295635 and 7295637).
Branches older than 10.0.8 aren't mentioned in the descriptions. Not being mentioned doesn't mean not affected: check the IBM bulletin and your branch's support status.
Detection
- Administrative logins from unusual addresses or at odd hours, especially without going through your usual directory or IdP (the hard-coded credential and authentication bypass CVEs)
- Gateway or catalog configuration changes that don't match any planned change
- Organization ownership changes and unexpected new accounts or members on the portal
- Outbound requests from the platform to unusual internal addresses or to
169.254.169.254(SSRF) - Submitted API definitions with unusual external references (CVE-2026-17299) or XML external entities (CVE-2026-16884)
- Unexpected child processes on API Connect hosts or containers (CVE-2026-17402)
Mitigation
1. Install the fixed release IBM specifies
With 35 critical CVEs, 14 of them unauthenticated, no workaround replaces the upgrade. 12.1 is the most exposed branch: it carries all 35.
2. Shrink exposure in the meantime
- Take admin interfaces (manager, API Connect cloud management) off the internet: only the developer portal and the gateway have any reason to be public, and even that deserves scrutiny
- Restrict open self-registration on the developer portal, since 21 CVEs need an account
- Limit the platform's outbound access to the internal network to what's strictly required, to contain the SSRFs
3. After upgrading
- Rotate admin credentials and integration secrets (directory, IdP, gateway keys)
- Revoke access tokens issued during the exposure window (CVE-2026-16720, CVE-2026-17297)
- Review the list of administrators, organizations and their owners
Why Continuous Monitoring of Your IBM Stack Matters
Thirty-five critical CVEs on the same day, none analyzed by NVD, no CPE configuration: a tool that relies on CPE data alone won't see anything for weeks — and those are exactly the weeks when technical details are most likely to start circulating.
With cveo.tech, track your IBM platforms with their exact version and get alerted as soon as a CVE affects them, including those NVD hasn't analyzed yet.