Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

mcp-framework

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7npmAmendedPublished

    MCP-Framework: Unbounded memory allocation in readRequestBody allows denial of service via HTTP transport

    CVE-2026-39313 · GHSA-353c-v8x9-v7c3

    Affected
    • npm mcp-framework <= 0.2.21
    Fixed in
    0.2.22· Vendor fix available
    Issue
    The readRequestBody() function in src/transports/http/server.ts concatenates HTTP request body chunks into a string with no size limit, allowing a remote unauthenticated attacker to crash the server via memory exhaustion with a single large HTTP POST request. Details File: src/transports/http/server.ts, lines 224-240 A maxMessageSize configuration value exists in DEFAULTHTTPSTREAMCONFIG (4MB, defined in src/transports/http/types.ts line 124) but is never enforced in readRequestBody(). This creates a false sense of security. PoC Local testing with 50MB POST payloads against the vulnerable readRequestBody() function: | Trial | Payload | RSS growth | Time | Result | |-------|---------|-----------|------|--------| | 1 | 50MB | +197MB | 42ms | Vulnerable | | 2 | 50MB | +183MB | 46ms | Vulnerable | | 3 | 50MB | +15MB | 43ms | Vulnerable | | 4 | 50MB | +14MB | 32ms | Vulnerable | | 5 | 50MB | +65MB | 38ms | Vulnerable | Reproducibility: 5/5 (100%) Impact - Denial of Service: Any…

    Recommended action: Upgrade to 0.2.22 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →