Quick answers
- Is CVE-2026-18486 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18486 being exploited in the wild.
- How severe is CVE-2026-18486?
- High severity, with a CVSS score of 8.8, published 4 September 2026.
- Which products and versions are affected?
- IBM ContextForge MCP Gateway <= v1.0.7.
- Is there a fix for CVE-2026-18486?
- A patch was published on 2026-09-04: Fix released in v1.0.8 (https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.8) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18486 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-18486?
- Check whether you run IBM Contextforge or IBM ContextForge MCP Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a jq filter injection in the jsonpath_filter field, where improper input validation allows authenticated users with developer privileges to execute unrestricted jq built-in functions like $ENV. The vulnerable component fails to sandbox or restrict jq program execution, allowing attackers to read environment variables containing JWT_SECRET_KEY, AUTH_ENCRYPTION_SECRET, DATABASE_URL, REDIS_URL, and BASIC_AUTH_PASSWORD. The attack requires prior authentication as a developer user (PR:L), involves no user interaction, and can achieve credential disclosure and privilege escalation. The fix is available in v1.0.8; deployments must upgrade and rotate all sensitive credentials listed above.
Affected products
- IBM ContextForge MCP Gateway <= v1.0.7
Timeline
- 2026-09-04: disclosed
- 2026-09-04: patched: Fix released in v1.0.8 (https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.8)