6 matches found
CVE-2026-78573
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.7 are vulnerable to administrative takeover due to default credentials (CWE-1392). Three password fields—platform_admin_password, default_user_password, and basic_auth_password—ship with the publicly known value "changeme" . When an operator...
CVE-2026-77822
IBM ContextForge MCP Gateway (versions ≤ v1.0.8) is vulnerable to server-side request forgery (SSRF) via DNS rebinding in its A2A invocation endpoint (POST /a2a/{agent_name}/invoke). Unlike other outbound egress paths, this endpoint does not pin the DNS-resolved IP at connection time, allowing a ...
CVE-2026-18905
IBM ContextForge MCP Gateway (mcp-contextforge-gateway) versions up to v1.0.6 are vulnerable to a DNS rebinding attack that enables server-side request forgery (SSRF) . The gateway validates REST tool target URLs only once at tool-registration time; when the same tool is later invoked, the stored...
CVE-2026-18489
IBM ContextForge MCP Gateway – Translate utility (≤ 1.0.8) is affected by a cross-client credential context confusion in the Translate service (mcpgateway/translate.py) when the --enable-dynamic-env flag is active. The service maps HTTP request headers (e.g. Authorization) into a shared stdio sub...
CVE-2026-18486
IBM ContextForge MCP Gateway (≤ v1.0.7) is vulnerable to credential disclosure and privilege escalation via improper validation of jq filters . An authenticated user with developer privileges can supply a malicious jq program in the jsonpath_filter field that executes unrestricted built-in functi...
CVE-2026-77825
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.8 is vulnerable to a path traversal flaw in the Admin API log-download endpoint (GET /v1/admin/logs/file). The vulnerability stems from the use of str.startswith() for path confinement, which lacks proper boundary validation. This allows an ...