Description

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information from internal network resources due to server-side request forgery. Destination checks on outbound requests can be bypassed, which could allow the server to reach internal systems that should be blocked.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.2",
  "pubDate": "2026-11-07T05:18:47.250Z",
  "pubdate": "2026-11-07T05:18:47.250Z",
  "executiveSummary": "IBM API Connect versions 12.1.0.0 through 12.1.1.2 are susceptible to a Server-Side Request Forgery (SSRF) vulnerability. This flaw allows a remote, authenticated attacker to manipulate the API gateway to initiate unauthorized outbound requests to internal network resources.\nThe vulnerability stems from improper validation of outbound destination targets, effectively bypassing implemented security controls intended to restrict the gateway's network reach.\nSuccessful exploitation grants the attacker the ability to interact with internal systems that are otherwise shielded from direct external access. This could lead to sensitive information disclosure, unauthorized data access, or the mapping of internal network infrastructure.\nBecause the vulnerability requires the attacker to be authenticated, the scope is restricted to users with valid access credentials, but the impact is significant due to the capability to pivot from the API gateway into the internal trusted network segment.\nThis vulnerability highlights a failure in the request filtering mechanism for outbound traffic, necessitating strict adherence to network segregation and updated security configurations to prevent lateral movement and data exfiltration.",
  "technicalDetails": "The vulnerability resides within the outbound request handling mechanism of IBM API Connect. Specifically, the API gateway fails to correctly enforce destination validation policies when processing requests initiated by the server. This indicates an insufficient sanitization or verification process for user-supplied or metadata-driven outbound URLs.\nThe attack flow begins when an authenticated attacker submits a request that leverages the gateway's functionality to fetch external or internal resources. By manipulating the destination parameters, the attacker can force the server to initiate an HTTP(S) request to arbitrary internal endpoints—such as metadata services, internal databases, or management consoles—that reside behind the API gateway's firewall.\nThe core issue is a bypass of the internal resource protection logic. Even if the system is configured to block requests to non-public addresses (e.g., localhost, private IP ranges like 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16), the lack of robust destination validation allows the SSRF payload to traverse these security boundaries.\nExploitation does not require elevated privileges beyond the initial authenticated access, meaning any user capable of triggering outbound gateway functions can potentially utilize this vector. Once the request is forwarded, the server acts as a proxy, effectively masquerading the attacker's request as legitimate internal traffic originating from the API Connect node.\nPost-exploitation, the attacker can receive the responses from the targeted internal resources, potentially obtaining sensitive configuration data, environment variables, or credentials. Furthermore, if the targeted internal services do not require secondary authentication, the attacker can interact with internal APIs, enabling a range of further malicious activities including unauthorized command execution or information harvesting.\nThe scope of the affected component is the outbound request handler within IBM API Connect versions 12.1.0.0 through 12.1.1.2. The lack of a strict allowlist mechanism for permitted egress destinations is the primary driver of this security risk."
}