Read the docs
TI-2026-71764 Aliases CVE-2026-53709

Hardcoded JWT secret in MCP Context Forge enables admin token forgery

Priority HIGH 82CWE-1188Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

MCP Context Forge before 1.0.2 ships a hardcoded default JWT_SECRET_KEY in its source and .env.example file. The token verification code accepts HS256 tokens signed with that key, so a remote unauthenticated attacker can forge tokens that grant platform administrator access without a database account (CWE-798). Forged access survives password rotation, account deletion and session revocation while the key stays configured, allowing administrative disclosure, modification and service disruption.

Written with Claude Haiku 5.5 from the sources below · 2026-10-27

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00603 49th percentileScored 2026-11-07
Fix Fixed mcp-context-forge (IBM): 1.0.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
IBMmcp-context-forgebefore 1.0.21.0.2Patch availableCNA
  • mcp-context-forge VendorIBM Affected before 1.0.2 Fixed in 1.0.2 Patch available CNA

Remediation

Upgrade IBM mcp-context-forge to version 1.0.2, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-27

  • Fix · CNA mcp-context-forge (IBM) Fixed in 1.0.2

Timeline

  1. 2026-10-13 Threatist record created from CVE-2026-53709
  2. 2026-10-18 CISA SSVC decision points changed
  3. 2026-10-18 Priority changed: MEDIUM → HIGH

References

Other 3

  • TI-2026-08085 Unauthenticated Remote Code Execution via Auto-Login Bypass and Code Validation KEVCVSS 3.1CRITICAL 9.8
  • TI-2022-23774 IBM Aspera Faspex code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2020-03794 Improper authentication in IBM Data Risk Manager KEVCVSS 3.1CRITICAL 9.8
  • TI-2019-03441 Code injection in IBM Planning Analytics KEVCVSS 3.1CRITICAL 9.8
  • TI-2017-03639 Improper handling of exceptional conditions in Apache Struts KEVCVSS 3.1CRITICAL 9.8
  • TI-2015-06198 Serialized-object interfaces in certain IBM analytics, business solutions, cognitive, IT… KEVCVSS 3.1CRITICAL 9.8
See all 9711 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences