Quick answers
- Is CVE-2026-77825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77825 being exploited in the wild.
- How severe is CVE-2026-77825?
- Medium severity, with a CVSS score of 4.9, published 24 September 2026.
- Which products and versions are affected?
- IBM ContextForge MCP Gateway 1.0.0 through 1.0.8.
- Is there a fix for CVE-2026-77825?
- A patch was published on 2026-09-24: Version 1.0.9 or later fixes the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77825 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-77825?
- Check whether you run IBM ContextForge MCP Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the Admin API endpoint GET /v1/admin/logs/file due to improper boundary validation using string prefix matching (str.startswith()) instead of proper canonicalization. An authenticated admin can craft filenames that resolve to sibling directories sharing a common path prefix with the configured LOG_FOLDER, allowing unauthorized file disclosure. The fix uses proper path validation and is available in version 1.0.9.
Affected products
- IBM ContextForge MCP Gateway 1.0.0 through 1.0.8
Timeline
- 2026-09-24: disclosed
- 2026-09-24: patched: Version 1.0.9 or later fixes the vulnerability