Description

IBM 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 authenticated attacker to perform arbitrary file reads and server-side request forgery due to unrestricted resolution of external references. Externally referenced content in submitted definitions is not sufficiently restricted when processed, and the retrieved content could be returned to the attacker.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.6",
  "pubDate": "2026-11-07T05:18:37.700Z",
  "pubdate": "2026-11-07T05:18:37.700Z",
  "executiveSummary": "IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 are susceptible to arbitrary file read and Server-Side Request Forgery (SSRF) vulnerabilities.\nThe vulnerability stems from improper handling of external references within submitted API definitions, which allows the processing engine to resolve and fetch unauthorized content.\nA remote authenticated attacker can exploit this flaw by submitting crafted definitions containing external references, forcing the application to perform requests to arbitrary internal or external resources.\nSuccessful exploitation permits the exfiltration of sensitive local files or the use of the API Connect infrastructure as a proxy to interact with internal network services, bypassing perimeter security controls.\nThis vulnerability poses a significant risk to the confidentiality and integrity of the application environment, necessitating immediate attention to remediation through patch deployment or configuration adjustments.\nExploitation requires the attacker to hold valid authentication credentials for the platform, though the level of privilege required beyond basic authentication is minimal for performing the requested actions.",
  "technicalDetails": "The vulnerability exists within the component responsible for parsing and resolving external references in submitted API definitions (e.g., OpenAPI or AsyncAPI specifications).\nThe root cause is the lack of sufficient restriction or validation on the URIs provided within the 'ref' fields or other external resource headers when the parser resolves external dependencies.\nWhen an authenticated user submits a definition, the API Connect engine attempts to dereference these external links. Because the parser does not effectively sanitize or whitelist the requested endpoints, it can be coerced into accessing local file system resources via schemes like 'file://' or reaching internal network endpoints unreachable from the public internet.\nThe attack flow follows a structured pattern: First, the attacker crafts a malicious API definition file that embeds a payload targeting a specific file path (e.g., '/etc/passwd' or internal configuration files) or an internal network IP address (e.g., internal metadata services or private APIs).\nSecond, the attacker submits this definition to the API Connect management or developer portal interface using their authenticated session.\nThird, the backend processing component, acting with the server's identity, executes an HTTP GET request or file system read operation to resolve the referenced resource.\nFourth, the service processes the retrieved content and, depending on the implementation, potentially reflects the contents of the file or the response from the internal service back to the attacker in the API response or logs.\nThis behavior constitutes a Server-Side Request Forgery (SSRF) because the server is used as a proxy to issue unauthorized requests on behalf of the attacker. Simultaneously, it constitutes an Arbitrary File Read vulnerability when the 'file://' protocol is successfully leveraged to bypass local directory restrictions.\nBecause the server component performing the resolution often resides within the trusted internal network perimeter, the impact extends beyond the application itself, potentially allowing the attacker to probe internal microservices, cloud metadata services, or other infrastructure endpoints that are not exposed to the public.\nAffected systems include IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2, requiring authenticated access to trigger the flaw."
}