IBM ContextForge MCP Gateway vulnerabilities

IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.7 allow a remote attacker to gain administrative access due to the use of default credentials.

A Server-Side Request Forgery (SSRF) vulnerability in IBM ContextForge MCP Gateway versions 0.1.0 through 1.0.5. An authenticated user with gateway creation privileges can perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints by supplying a malicious oauth_config.token_url parameter during OAuth-enabled gateway registration.

IBM ContextForge MCP Gateway 1.0.0 through 1.0.8 was vulnerable to path traversal in its Admin API log-download endpoint (GET /v1/admin/logs/file). The path confinement check uses str.startswith() rather than proper boundary validation, allowing an authenticated admin to read .log, .jsonl, and .json files outside the configured LOG_FOLDER.

IBM ContextForge MCP Gateway <= v1.0.4 allows an authenticated user to bypass protection mechanisms due to incomplete recursive inspection of nested payload content. The flaw enables evasion of security controls through content hidden in nested structures.

IBM ContextForge MCP Gateway - Translate utility <= 1.0.8 MCP Context Forge could allow a remote attacker to obtain sensitive information from other sessions due to exposure of data elements to the wrong session.

IBM ContextForge MCP Gateway <= v1.0.7 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive credentials and escalate privileges due to improper validation of jq filters.

IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery via DNS rebinding.