IBM Contextforge vulnerabilities

6 vulnerabilities

Known vulnerabilities in IBM Contextforge, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

9.6CVE-2026-77822ibmcontextforge+1
EPSS score
0.37%
IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery via DNS rebinding.4.9CVE-2026-77825ibmcontextforge+1
EPSS score
0.32%
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` by supplying a filename that resolves into a sibling directory whose absolute path shares the log directory's string prefix.7.4CVE-2026-18489ibmcontextforge+1
EPSS score
0.26%
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.8.8CVE-2026-18486ibmcontextforge+1
EPSS score
0.33%
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.7.7CVE-2026-18905ibmcontextforge+1
EPSS score
0.34%
IBM ContextForge MCP Gateway (`mcp-contextforge-gateway`) <= v1.0.6 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive information due to a DNS rebinding vulnerability during tool invocation.9.8CVE-2026-78573ibmcontextforge+1
EPSS score
0.58%
IBM ContextForge MCP Gateway 1.0.0 through 1.0.7 could allow a remote attacker to gain administrative access due to the use of default credentials.