IBM ContextForge MCP Gateway
IBM ContextForge MCP Gateway is affected by an information exposure vulnerability
IBM ContextForge MCP Gateway 1.0.0 through 1.1.0 could allow an attacker to replay identity propagation claims signatures or expose sensitive user identity information to third-party MCP servers due to static signature payloads and missing per-gateway configuration checks during tool invocation.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.0.0, <= 1.1.0
Mitigation
IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway v1.0.0-v1.1.0Upgrade to v1.1.1 immediately [ Release notes https://github.com/IBM/mcp-context-forge/releases/tag/v1.1.1 ]
Workaround
IBM strongly recommends upgrading to the fixed version. If you cannot update disable identity propagation globally (set `IDENTITY_PROPAGATION_ENABLED=false`) so that no upstream MCP server receives user identity information, and restrict access to the gateway to trusted users.
References
- Vendor advisory ibm.com/support/pages/node/7296489
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 suspicious or fake
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| webpro255/awesome-ai-agent-attacks | 7 Apr 2026 −220 d | 91 | Suspicious · score 80
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.