CVE-2026-18489
IBM ContextForge Translate is affected by cross-client credential context confusion
- Published
- Updated
- Reserved
- Assigned by
- ibm
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| ibmCNA (assigner) | 3.1 | High7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVDNVD · Analyzed | 3.1 | High7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.42% · top 63% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.4.
Weakness
Affected products
IBM · ContextForge MCP Gateway - Translate utility
- affected <= 1.0.8
What to do
Solution: 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 (1)
- https://www.ibm.com/support/pages/node/7286056 (opens in a new tab)vendor-advisorypatch
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2026-18489)Record last updated .