contextforge vulnerabilities and fixes
Recent CVEs affecting contextforge, with upgrade or downgrade steps. 6 tracked.
contextforge has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 6. Most recent: 2026-09-24. Highest priority: CVE-2026-78573 (score 51/100).
- CVE-2026-77825 MEDIUM 4.9 UPGRADE IBM ContextForge MCP Gateway 1.0.0 through 1.0.8 was vulnerable to path traversal in its Admin API log-downloa
- CVE-2026-78573 CRITICAL 9.8 UPGRADE IBM ContextForge MCP Gateway 1.0.0 through 1.0.7 could allow a remote attacker to gain administrative access d
- CVE-2026-18905 HIGH 7.7 UPGRADE IBM ContextForge MCP Gateway (`mcp-contextforge-gateway`) <= v1.0.6 MCP Context Forge could allow a remote aut
- CVE-2026-77822 HIGH 8.2 UPGRADE IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due t
- CVE-2026-18486 HIGH 8.8 UPGRADE IBM ContextForge MCP Gateway <= v1.0.7 MCP Context Forge could allow a remote authenticated attacker to obtain
- CVE-2026-18489 HIGH 7.4 UPGRADE IBM ContextForge MCP Gateway - Translate utility <= 1.0.8 MCP Context Forge could allow a remote attacker to o
FAQ
How do I fix contextforge vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is contextforge being exploited right now?
None of the tracked contextforge CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which contextforge CVE should I patch first?
CVE-2026-78573 currently ranks highest (51/100): IBM ContextForge MCP Gateway 1.0.0 through 1.0.7 could allow a remote attacker to gain administrative access d.