Categories
CVE-2026-57494

Vulnerability in @agenticmail/api (CVE-2026-57494)

Summary

Vulnerability in @agenticmail/api (CVE-2026-57494). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/agenticmail/tasks/pending. Mitigation: upgrade to 0.9.64 or later.

Original description

The description as published by the source.

AgenticMail gives AI agents real email addresses and phone numbers. In @agenticmail/api prior to version 0.9.64, a low-privileged authenticated AgenticMail agent can enumerate another agent's pending/claimed tasks by supplying the target agent name to GET /api/agenticmail/tasks/pending?assignee=. The returned task objects include the task IDs and payloads. The same task IDs can then be used with the capability-style task mutation endpoints (/tasks/:id/claim, /tasks/:id/result, /tasks/:id/complete, /tasks/:id/fail) to claim, complete, or fail tasks assigned to a different agent. Because ordinary authenticated agents can discover agent names through GET /api/agenticmail/accounts/directory, the task ID effectively stops being a secret capability. This turns the intended capability model into a cross-agent authorization bypass. Version 0.9.64 contains a fix.

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-57494 has been found in @agenticmail/api.
Attackers can target a specific entry point like GET /api/agenticmail/tasks/pending over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @agenticmail/api to 0.9.64 or later.
If unsure, ask your IT team or search "@agenticmail/api CVE-2026-57494" on the vendor's site.

CVE-2026-57494 (@agenticmail/api) — CWE-639
Attack surface: GET /api/agenticmail/tasks/pending / GET /api/agenticmail/accounts/directory / GET /accounts/directory / GET /tasks/pending
Patched: 0.9.64 — 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-639) exists in @agenticmail/api. Attackers reach the vulnerable code path via GET /api/agenticmail/tasks/pending.

📍 Affected scope

Check the vendor advisory for the affected versions of @agenticmail/api. Attack surface: GET /api/agenticmail/tasks/pending / GET /api/agenticmail/accounts/directory / GET /accounts/directory / GET /tasks/pending.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.9.64.

🛡️ 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 GET /api/agenticmail/tasks/pending requests with malformed payloads or SQL meta-characters. Run grep -r '@agenticmail/api' . 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

  1. 1
    Identify exposure identify
    grep -r '@agenticmail/api' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @agenticmail/api を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /api/agenticmail/tasks/pending' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/agenticmail/tasks/pending への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade @agenticmail/api to 0.9.64

    ステージング環境で 0.9.64 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /api/agenticmail/tasks/pending on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @agenticmail/api
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.9.64"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details