{"answers":{"affected":"2 open source packages ship an affected version, including mcp-framework.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39313 exists.","fix":"Upgrade mcp-framework to 0.2.22 or later.","what":"CVE-2026-39313 is a high-severity denial of service vulnerability in QuantGeekDev mcp-framework, published on 16 Apr 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-39313 and fix it if it is affected.\n\nWhat it is: CVE-2026-39313 is a high-severity denial of service vulnerability in QuantGeekDev mcp-framework, published on 16 Apr 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-39313 exists.\n\nAffected packages and fixed versions:\n- mcp-framework (npm): affected all versions; fixed in 0.2.22\n- mcp-framework (npm): affected all versions; fixed in 0.2.22\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-39313/ (Markdown: https://insights.sbomify.com/CVE-2026-39313/index.md)","id":"CVE-2026-39313","markdown":"https://insights.sbomify.com/CVE-2026-39313/index.md","name":"CVE-2026-39313","record":{"aliases":["GHSA-353c-v8x9-v7c3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP server framework","requires_auth":"none","summary":"Remote attackers can crash MCP servers by sending large HTTP requests due to unbounded memory allocation in the readRequestBody function.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"mcp-framework is a framework for building Model Context Protocol (MCP) servers. In versions 0.2.21 and below, the readRequestBody() function in the HTTP transport concatenates request body chunks into a string with no size limit. Although a maxMessageSize configuration value exists, it is never enforced in readRequestBody(). A remote unauthenticated attacker can crash any mcp-framework HTTP server by sending a single large POST request to /mcp, causing memory exhaustion and denial of service. This issue has been fixed in version 0.2.22.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"MCP-Framework: Unbounded memory allocation in readRequestBody allows denial of service via HTTP transport","id":"CVE-2026-39313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"CUPS has an integer underflow in `_ppdCreateFromIPP` causes root cupsd crash via negative `job-password-supported`","id":"CVE-2026-39314"},"packages":[{"ecosystem":"npm","fixed":["0.2.22"],"introduced":["0"],"last_affected":[],"package":"mcp-framework","purl":null,"source":"GHSA-353c-v8x9-v7c3"},{"ecosystem":"npm","fixed":["0.2.22"],"introduced":["0"],"last_affected":[],"package":"mcp-framework","purl":"pkg:npm/mcp-framework","source":"GHSA-353c-v8x9-v7c3"}],"prev":{"headline":"Pre-Auth EAP-TLS DoS on SoftEther VPN Developer Edition","id":"CVE-2026-39312"},"products":["mcp-framework"],"published":"2026-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-04-17","vendors":["QuantGeekDev"]},"summary":"Remote attackers can crash MCP servers by sending large HTTP requests due to unbounded memory allocation in the readRequestBody function.","url":"https://insights.sbomify.com/CVE-2026-39313/"}