CVE-2026-18486: IBM ContextForge MCP Gateway is affected by credential disclosure and privilege escalation via jq filter execution
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
IBM ContextForge MCP Gatewayto a version that resolves this vulnerability.Fixed in v1.0.8 - Configuration
When upgrading to v1.0.8, ensure `AUTH_ENCRYPTION_SECRET` is updated to the more complex value required starting in v1.0.8.
IBM ContextForge MCP Gateway AUTH_ENCRYPTION_SECRET = Use the more complex `AUTH_ENCRYPTION_SECRET` required from version v1.0.8 onward - Operational
Before upgrading from IBM ContextForge MCP Gateway <= v1.0.7 to v1.0.8, stop the gateway and run the one-shot re-encryption script `mcpgateway/scripts/migrate_enc_secret.py` using the old and new keys.
- Operational
Rotate the secrets on any IBM ContextForge MCP Gateway deployment running prior versions (<= v1.0.7): `JWT_SECRET_KEY`, `AUTH_ENCRYPTION_SECRET`, `DATABASE_URL`, `REDIS_URL`, and `BASIC_AUTH_PASSWORD`.
Event History
Frequently Asked Questions
Who can exploit this issue?
A remote attacker must be authenticated and have the privileges needed to submit or execute jq filters. No user interaction is required.
What is the affected version range?
IBM ContextForge MCP Gateway, also referred to as MCP Context Forge, is affected through version 1.0.7, including version 1.0.7.
What could exploitation allow?
An attacker could obtain sensitive credentials and escalate privileges. The reported impact includes loss of confidentiality, integrity, and availability.