← Back
CVE-2026-50287
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-306) exists in @agenticmail/mcp. Attackers reach the vulnerable code path via `Authorization header` without authentication.
📍 Affected scope
@agenticmail/mcp — . Attack surface: Authorization header / `AGENTICMAIL_MASTER_KEY` / `setup_guide` / `setup_email_relay`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.9.27**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @agenticmail/mcp to 0.9.27ステージング環境で 0.9.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@agenticmail/mcp
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.9.27"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-50287
- package https://github.com/agenticmail/agenticmail
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/agenticmail/agenticmail/commit/7b9b05d973676e9f3d097c08b8e649f59bfc15d0
- web https://github.com/agenticmail/agenticmail/commit/7d1791da7c8c8bd4e70d7081db48e18ab55f6736
- web https://github.com/agenticmail/agenticmail/blob/7b9b05d973676e9f3d097c08b8e649f59bfc15d0/CHANGELOG.md?plain=1#L10
- web https://github.com/agenticmail/agenticmail/blob/7b9b05d973676e9f3d097c08b8e649f59bfc15d0/packages/mcp/README.md?plain=1#L13
- web https://github.com/agenticmail/agenticmail/blob/7b9b05d973676e9f3d097c08b8e649f59bfc15d0/packages/mcp/src/index.ts#L311
- web https://github.com/advisories/GHSA-63gr-g7jc-v8rg