Skip to content

← Public intelligence

npm package

@agenticmail/mcp

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

    @agenticmail/mcp Missing Authentication for Critical Function

    CVE-2026-50287 · GHSA-63gr-g7jc-v8rg

    Affected
    • npm @agenticmail/mcp < 0.9.27
    Fixed in
    0.9.27· Vendor fix available
    Issue
    AgenticMail MCP HTTP authorization bypass Summary @agenticmail/mcp exposes a Streamable HTTP transport when started with --http or MCPHTTP=1. In that mode, the /mcp endpoint accepts requests without any HTTP authentication layer. A remote client can initialize a session and call tools directly. The problem is that the MCP server also exposes tools documented as requiring AGENTICMAILMASTERKEY, and the server process forwards those calls using its own configured master key. As a result, any client that can reach the MCP HTTP port can invoke master-only operations without knowing the master key. Impact An unauthenticated network client can invoke master-key-only MCP tools through the server, including administrative and gateway actions. Confirmed with a read-only tool: - setupguide The same path reaches higher-impact tools such as: - setupemailrelay - setupemaildomain - deleteagent - cleanupagents - sendtestemail Affected Code - packages/mcp/src/index.ts - packages/mcp/src/tools.ts -…

    Recommended action: Upgrade to 0.9.27 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 →