Skip to content

Advisory template

Fill this in for a vulnerability you found with mcpwn, then follow the disclosure process in ../SECURITY.md. Report privately to the maintainer first; allow remediation time before publishing.

One sentence: what the vulnerability is and its impact.

  • Package / server: <name>
  • Versions: <= x.y.z
  • Transport: stdio / Streamable HTTP
  • Component: <tool name> (tools/call) / tools/list / resource / prompt

CVSS vector + score, or qualitative (low/medium/high/critical) with rationale.

What the flaw is and why it exists (the missing/insufficient check).

Terminal window
mcpwn -i -l evidence.jsonl -- npx -y <server> <args>
  1. Drive the client to call <tool>.
  2. Hold the tools/call request; edit arguments to:
    { "...": "<payload>" }
  3. Forward and observe the response / side effect proving the issue.

Attach the relevant lines from evidence.jsonl (redact any real secrets).

What an attacker gains: file read outside scope, SSRF to metadata service, RCE, data exfiltration via a coerced agent, etc.

The concrete fix (e.g. “resolve with fs.realpath and check resolved.startsWith(allowedDir + path.sep) before access”).

  • YYYY-MM-DD - reported privately to maintainer
  • YYYY-MM-DD - fix released / 90-day window elapsed
  • YYYY-MM-DD - public disclosure

Found with mcpwn.