Metrics
Affected Vendors & Products
No advisories yet.
Solution
IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gatewayv1.0.0 - v1.0.8Upgrade to version 1.0.9 or later. See release notes https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.9
Workaround
None. IBM strongly recommends upgrading to the fixed version. As temporary mitigations until the update can be applied: 1. Disable the Admin API (`MCPGATEWAY_ADMIN_API_ENABLED=false`) if administrative endpoints are not required.
| Link | Providers |
|---|---|
| https://www.ibm.com/support/pages/node/7289314 |
|
Thu, 24 Sep 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | IBM ContextForge MCP Gateway is affected by path traversal | |
| First Time appeared |
Ibm
Ibm contextforge Mcp Gateway |
|
| Weaknesses | CWE-22 | |
| CPEs | cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.0:*:*:*:*:*:*:* cpe:2.3:a:ibm:contextforge_mcp_gateway:1.0.8:*:*:*:*:*:*:* |
|
| Vendors & Products |
Ibm
Ibm contextforge Mcp Gateway |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: ibm
Published:
Updated: 2026-09-24T14:21:18.507Z
Reserved: 2026-08-21T14:42:05.183Z
Link: CVE-2026-77825
No data.
Status : Awaiting Analysis
Published: 2026-09-24T15:17:38.560
Modified: 2026-09-24T19:41:16.513
Link: CVE-2026-77825
No data.
OpenCVE Enrichment
No data.