Vulnerability in @agenticmail/mcp (CVE-2026-50287)
Summary
Vulnerability in @agenticmail/mcp (CVE-2026-50287). Risk of unauthorized operations or information disclosure. Exploitable via Authorization header. Mitigation: upgrade to 0.9.27 or later.
Original description
The description as published by the source.
AgenticMail gives AI agents real email addresses and phone numbers. Prior to version 0.9.27, @agenticmail/mcp exposes a Streamable HTTP transport when started with --http or MCP_HTTP=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. This issue has been patched in version 0.9.27.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50287 has been found in @agenticmail/mcp.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @agenticmail/mcp to 0.9.27 or later.
If unsure, ask your IT team or search "@agenticmail/mcp CVE-2026-50287" on the vendor's site.
CVE-2026-50287 (@agenticmail/mcp) — CWE-306
Attack surface: Authorization header / AGENTICMAIL_MASTER_KEY / setup_guide / setup_email_relay
Patched: 0.9.27 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in @agenticmail/mcp. Attackers reach the vulnerable code path via Authorization header.
Check the vendor advisory for the affected versions of @agenticmail/mcp. Attack surface: Authorization header / AGENTICMAIL_MASTER_KEY / setup_guide / setup_email_relay.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.9.27.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@agenticmail/mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@agenticmail/mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@agenticmail/mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @agenticmail/mcp to 0.9.27ステージング環境で 0.9.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com