CVE-2026-53709: fallo crítico en IBM mcp-context-forge
MCP Context Forge: Hardcoded default JWT_SECRET_KEY shipped in source and .env.example enables pre-authentication platform admin token forgery
Publicada el · Actualizada el
28Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 9.8epss 0.6%
probabilidad de explotación
0.6%top 51% de las CVE
explotación observada
noninguna fuente lo reporta
MCP Context Forge is an MCP gateway and administrative platform. Prior to 1.0.2, mcpgateway/config.py and .env.example ship a known JWT_SECRET_KEY, while verify_jwt_token() accepts HS256 tokens signed with that key and get_current_user() creates a platform administrator when the token subject matches PLATFORM_ADMIN_EMAIL and REQUIRE_USER_IN_DB is false. A remote unauthenticated attacker can therefore mint accepted administrator tokens without a database account. While the vulnerable signing key remains configured and the platform-admin bootstrap remains enabled, forged access survives password rotation, account deletion, and session revocation, allowing administrative disclosure, modification, and service disruption. This issue is fixed in version 1.0.2.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Productos afectados
IBM · mcp-context-forgeCVEs relacionadas — IBM mcp-context-forge
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-53710CRITICALMCP Context Forge: RestrictedPython sandbox bypass via getattr builtin in python_sandbox_serverEPSS 1.1%CVE-2026-53711MEDIUMMCP ContextForge: Global Prompts stored cross-site scripting compromises the Admin UIEPSS 0.4%CVE-2026-53708MEDIUMContextForge: DNS TOCTOU race condition causes SSRF protection bypass (`/admin/gateways/test`)EPSS 0.4%