Security Resilience

CVE-2026-17131

SSRF in Ibm Api Connect 12.1.0.0 – 12.1.1.3

Published
07 November 2026
Modified
12 November 2026
Patch / advisory
CVSS Score v3.1 9.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS Score 0.0042 37th percentile
Risk Priority 66 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-17131 is a critical-severity SSRF (CWE-918) vulnerability in Ibm Api Connect. Its CVSS base score is 9.3 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Proxy (T1090); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SC-7 (Boundary Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to server-side request forgery. Restrictions on outbound requests can be bypassed, so the server could be made to contact unintended destinations and return the…

more

response.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1090 Proxy Command And Control
Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure.
T1528 Steal Application Access Token Credential Access
Adversaries can steal application access tokens as a means of acquiring credentials to access remote systems and resources.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1552.005 Cloud Instance Metadata API Credential Access
Adversaries may attempt to access the Cloud Instance Metadata API to collect credentials and other sensitive data.
T1018 Remote System Discovery Discovery
Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for Lateral Movement from the current system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-17285Same product: Ibm Api Connect
CVE-2026-16918Same product: Ibm Api Connect
CVE-2026-17299Same product: Ibm Api Connect
CVE-2026-17288Same product: Ibm Api Connect
CVE-2026-17188Same product: Ibm Api Connect
CVE-2026-17108Same product: Ibm Api Connect
CVE-2026-17306Same product: Ibm Api Connect
CVE-2026-17287Same product: Ibm Api Connect
CVE-2026-17294Same product: Ibm Api Connect
CVE-2026-17281Same product: Ibm Api Connect

Affected Assets

ibm
api connect
12.1.0.0 — 12.1.1.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
blocks

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
blocks

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's testing programme (code review, static analysis, vulnerability scanning, penetration testing, architecture review) covers every detection method CWE-918 rates High or Moderate, and the clause explicitly names code review for un-anticipated inputs and acceptance testing of acquired products, so no further act of finding is left over — the same logic the owner applied to A.8.29 finds CWE-89 = full.

blocks

A.8.20's firewall and network filtering controls (items i, j, n) can block a meaningful portion of SSRF exploitation paths — particularly outbound connections to internal networks, cloud metadata endpoints, and disallowed protocols — but the application-layer URL validation defect remains and SSRF can still be exploited via external attacker-controlled destinations, DNS rebinding, and allowed internal services, leaving a nameable remainder.

blocks

A.8.21's network connection controls, egress restrictions and monitoring of network service use can block some SSRF exploitation (e.g., preventing the server from reaching internal services, cloud metadata endpoints, or arbitrary ports), but the application-level URL-fetching vulnerability remains and can still be exploited against any destination the network permits.

blocks

Network segregation with gateway controls blocks SSRF exploitation against internal network resources (internal admin panels, cross-domain port scanning, internal services), which is a major portion of the weakness's damage surface, but the weakness remains exploitable for external destinations, localhost services, and cloud metadata endpoints that the segregation does not reach.

prevents

A.8.28 mandates secure coding principles that include URL/destination validation and allowlisting practices which, where followed, prevent SSRF from being introduced; but the clause is a practice-based control whose effect depends on developer implementation rigor, so it catches only a minority of instances — the same reading that graded A.8.28 -> CWE-502 and A.8.28 -> CWE-79 at `partial`, and the clause's declared ceiling on this verb.

finds

A.8.30's contractual requirements for acceptance testing (8.29) and evidence of testing for malicious content and known vulnerabilities cause SSRF to be discovered in delivered outsourced code, but the finding is performed by the testing programme A.8.30 contracts for rather than by A.8.30 itself, and the effect is reduced because it is mediated through a supplier relationship.

References