CVE-2026-77825: medium-severity vulnerability in IBM ContextForge MCP Gateway
IBM ContextForge MCP Gateway is affected by path traversal
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.9epss 0.3%
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Affected products
IBM · ContextForge MCP GatewayRelated CVEs — IBM ContextForge MCP Gateway
In the same product, most dangerous first.
CVE-2026-18486HIGHIBM ContextForge MCP Gateway is affected by credential disclosure and privilege escalation via jq filter executionEPSS 0.6%CVE-2026-78573CRITICALIBM ContextForge MCP Gateway is affected by use of default credentialsEPSS 0.6%CVE-2026-110189MEDIUMIBM ContextForge MCP Gateway is affected by a denial of service due to an incomplete list of disallowed jq inputsEPSS 0.5%CVE-2026-18484MEDIUMIBM ContextForge MCP Gateway is affected by a denial-of-service via tool name collision through slug normalizationEPSS 0.4%CVE-2026-77822HIGHIBM ContextForge MCP Gateway is affected by server-side request forgery (DNS rebinding) via the A2A agent invocation endpointEPSS 0.4%CVE-2026-110178MEDIUMIBM ContextForge MCP Gateway is affected by an improper access control vulnerability in configuration importEPSS 0.4%