Skip to content

Security: omer-ayhan/mcpmux

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.1.x Yes

Reporting a Vulnerability

Do not open a public issue for security vulnerabilities.

If you discover a security vulnerability in mcpmux, please report it privately through one of these channels:

Please include:

  • A description of the vulnerability
  • Steps to reproduce or a proof of concept
  • The potential impact
  • Suggested fix (if you have one)

Response Timeline

  • Acknowledgment: Within 48 hours of your report
  • Assessment: Within 5 business days
  • Fix (critical): Target release within 7 days
  • Fix (non-critical): Included in the next scheduled release

Scope

The following are considered security issues:

  • Upstream credential exposure through the gateway
  • Tool injection or unauthorized tool execution
  • Config parsing exploits (path traversal, code injection)
  • Bypassing excludeTools or allowHighRisk: false filtering
  • Denial of service through crafted queries

Disclosure

We follow coordinated disclosure. Once a fix is released, we will:

  1. Publish a GitHub Security Advisory
  2. Credit the reporter (unless they prefer to remain anonymous)
  3. Include details in the changelog

There aren’t any published security advisories