CVE-2026-77825: IBM ContextForge MCP Gateway is affected by path traversal
IBM ContextForge Gateway 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 LOGFOLDER by supplying a filename that resolves into a sibling directory whose absolute path shares the log directory's string prefix.
Other sources
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 LOGFOLDER by supplying a filename that resolves into a sibling directory whose absolute path shares the log directory's string prefix.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
IBM ContextForge MCP Gatewayto a version that resolves this vulnerability.Fixed in 1.0.9
Event History
Frequently Asked Questions
Which deployments are affected?
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.8 are affected. The issue is in the Admin API log-download endpoint at GET /v1/admin/logs/file.
What access does an attacker need?
An attacker must be authenticated as an administrator. No user interaction is required, and the vulnerable endpoint is reachable over the network.
What files could be exposed?
An authenticated administrator can read files outside the configured LOG_FOLDER when they are in a sibling directory whose absolute path shares the log directory's string prefix. The disclosed file types are .log, .jsonl, and .json.
How can I assess whether a system is exposed?
Check whether the gateway version is between 1.0.0 and 1.0.8 and whether the Admin API endpoint GET /v1/admin/logs/file is available. Exposure requires accessible files with the permitted extensions in a sibling directory matching the LOG_FOLDER path prefix condition.