IBM ContextForge MCP Gateway - Translate utility
IBM ContextForge Translate is affected by cross-client credential context confusion
IBM ContextForge MCP Gateway - Translate utility <= 1.0.8 MCP Context Forge could allow a remote attacker to obtain sensitive information from other sessions due to exposure of data elements to the wrong session.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 1.0.8
Mitigation
IBM strongly recommends addressing the vulnerability now. The IBM ContextForge Translate service is intended **only for local, single-session development use**. It does not provide the session isolation required for production or multi-client deployments. Users must ensure the Translate service is not exposed in any production capacity. PR [#6388]( https://github.com/IBM/mcp-context-forge/pull/6388) https://github.com/IBM/mcp-context-forge/pull/6388%29 (merged 2026-08-24) updates the product documentation to make this restriction explicit, removing previous guidance that could have implied multi-tenant production suitability.
Workaround
Do not use the IBM ContextForge Translate service in any production or multi-client environment. The service is designed exclusively for local development scenarios where only a single client session is expected. This applies regardless of whether `--enable-dynamic-env` is active. If the Translate service is currently running in a non-development environment: 1. Stop the Translate service and remove it from any production deployment immediately. 2. Rotate any credentials (API tokens, `Authorization` headers) that may have been mapped into the shared subprocess environment while multiple clients were connected. 3. Review audit logs for tool calls where the HTTP caller identity may not match the subprocess credential context.
References
- Vendor advisory ibm.com/support/pages/node/7286056
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.