{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53709 exists.","fix":"No fix has been published for CVE-2026-53709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53709 is a critical vulnerability in IBM mcp-context-forge, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53709 and fix it if it is affected.\n\nWhat it is: CVE-2026-53709 is a critical vulnerability in IBM mcp-context-forge, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53709 exists.\n\nAffected product: IBM mcp-context-forge. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53709/ (Markdown: https://insights.sbomify.com/CVE-2026-53709/index.md)","id":"CVE-2026-53709","markdown":"https://insights.sbomify.com/CVE-2026-53709/index.md","name":"CVE-2026-53709","record":{"aliases":["GHSA-m8rv-5m6m-32ff"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_read","data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"MCP gateway platform","requires_auth":"none","summary":"Remote attackers can forge admin tokens using a hardcoded JWT secret to gain full administrative control over the MCP Context Forge platform.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Hardcoded credentials in mcp-context-forge","id":"CVE-2026-53709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"MCP Context Forge: RestrictedPython sandbox bypass via getattr builtin in python_sandbox_server","id":"CVE-2026-53710"},"packages":[],"prev":{"headline":"ContextForge: DNS TOCTOU race condition causes SSRF protection bypass (`/admin/gateways/test`)","id":"CVE-2026-53708"},"products":["mcp-context-forge"],"published":"2026-10-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["IBM"]},"summary":"Remote attackers can forge admin tokens using a hardcoded JWT secret to gain full administrative control over the MCP Context Forge platform.","url":"https://insights.sbomify.com/CVE-2026-53709/"}