ContextForge MCP Gateway vulnerabilities
4 known vulnerabilities in ContextForge MCP Gateway from IBM. 4 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 8.1 High severity
ContextForge MCP Gateway: Improper Authentication
IBM ContextForge MCP Gateway 1.0.0 through 1.1.0 is vulnerable to improper credential handling because the X-Upstream-Authorization request header can override the gateway-managed upstream credential for OAuth (authorization_code and client_credentials), beare
- 7.4 High severity
ContextForge MCP Gateway: Authentication Bypass by Capture-replay
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 configur
- 8.8 High severity
ContextForge MCP Gateway: Exposure of Sensitive Information to an Unauthorized Actor
IBM ContextForge MCP Gateway <= v1.0.7 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive credentials and escalate privileges due to improper validation of jq filters.
- 9.6 Critical severity
ContextForge MCP Gateway: Server-Side Request Forgery
IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery via DNS rebinding.