Path Traversal in IBM ContextForge MCP Gateway (CVE-2026-77825)
Summary
Path traversal in IBM ContextForge MCP Gateway (CVE-2026-77825). Confidential information can be exposed externally. Exploitable via GET /v1/admin/logs/file.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-77825 has been found in IBM ContextForge MCP Gateway.
Attackers can target a specific entry point like GET /v1/admin/logs/file over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "IBM ContextForge MCP Gateway CVE-2026-77825" on the vendor's site.
CVE-2026-77825 (IBM ContextForge MCP Gateway) — CWE-22 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /v1/admin/logs/file / LOG_FOLDER
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in IBM ContextForge MCP Gateway. Attackers reach the vulnerable code path via GET /v1/admin/logs/file.
Check the vendor advisory for the affected versions of IBM ContextForge MCP Gateway. Attack surface: GET /v1/admin/logs/file / LOG_FOLDER.
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /v1/admin/logs/file requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで IBM ContextForge MCP Gateway を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'GET /v1/admin/logs/file' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /v1/admin/logs/fileへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /v1/admin/logs/file on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web ibm.com
- web nvd.nist.gov
- web github.com