CVE-2026-39313
DoS in mcp-framework HTTP server due to unbounded readRequestBody.
Is CVE-2026-39313 being exploited?
Not confirmed. CVE-2026-39313 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-39313?
CVE-2026-39313 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-39313?
Yes. A fix has been recorded for CVE-2026-39313. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-39313 affect?
CVE-2026-39313 affects mcp-framework <= 0.2.21, HTTP transport /mcp server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-39313?
Upgrade to 0.2.22+ to fix readRequestBody limit.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can crash HTTP server via oversized POST to /mcp, exhausting memory and causing DoS.
Patch when possible
- affected< 0.2.22
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.