Patchbay CVE database

1 published advisory covering public MCP server vulnerabilities · 0 open · 0 under coordinated-disclosure embargo.

What this is. A catalogue of concrete findings against specific MCP servers (or server versions), with a stable identifier you can cite. The CVE-PATCHBAY-YYYY-NNNN scheme is patchbay-assigned and separate from MITRE CVE — we fill the gap until MCP servers are routinely assigned CVEs through standard channels. Advisories move through embargoed (operator notified, 90 days to fix) → open (details published) → fixed (operator confirmed rotation / patch). Advisories that turn out to be false positives after verification are marked withdrawn and kept in the index so the retraction is also citable.
IDSeverityFindingTitleStatusPublished
CVE-PATCHBAY-2026-0001criticalSECRET-001WITHDRAWN: initial finding was a false positive (product URL slug matched OpenAI key regex) · withdrawn 2026-11-13 — false positivewithdrawn2026-11-13

OWASP MCP Top 10 (2025) overlay

How patchbay's checks and the public MCP CVE index break down across the ten OWASP MCP risk categories. OWASP MCP Top 10 · CVE index: mcp-security-project/mcp-cve-project (802 CVEs indexed, last synced 2026-11-13).

CategoryPublic CVEsPatchbay checks
MCP01
Token Mismanagement & Secret Exposure
133SECRET-001, SECRET-002, OAUTH-REVOCATION-001
MCP02
Privilege Escalation via Scope Creep
100AUDIENCE-001, AUDIENCE-002, SCOPE-001, SCOPE-002
MCP03
Tool Poisoning
2POISONING-001, ANNOTATIONS-001
MCP04
Software Supply Chain Attacks & Dependency Tampering
37MANIFEST-001, MANIFEST-002, SDK-CVE-001
MCP05
Command Injection & Execution
278URITEMPLATE-001
MCP06
Prompt Injection via Contextual Payloads
19POISONING-002, POISONING-003, SAMPLING-001
MCP07
Insufficient Authentication & Authorization
201AUTH-001, AUTH-002, AUTH-003, AUTH-004, AUTH-005, AUTH-006, AUTH-007, TRANSPORT-001, TRANSPORT-002, REDIRECT-001, REDIRECT-002, PKCE-001, PKCE-002, IMPLICIT-001, RESOURCE-001, HEADERS-001, ISS-001
MCP08
Lack of Audit and Telemetry
4— (not yet covered)
MCP09
Shadow MCP Servers
22— (not yet covered)
MCP10
Context Injection & Over-Sharing
6— (not yet covered)

Reporting a finding

Found something on a public MCP server? Email security@patchbay-mcp.dev. We will coordinate disclosure, assign a CVE-PATCHBAY identifier, and help you contact the operator. Include URL, finding category and evidence. We do not pay bounties, but we credit discoverers in the advisory.