← Back
GHSA-hjwc-26pj-v3pm
Vulnerability in @agenticmail/api (GHSA-hjwc-26pj-v3pm)
Summary
vulnerability in @agenticmail/api (GHSA-hjwc-26pj-v3pm). Risk of unauthorized operations or information disclosure. Exploitable via `GET /api/agenticmail/tasks/pending`. Mitigation: upgrade to `0.9.64` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-hjwc-26pj-v3pm** 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. CVSS score: ?/10.
What to do: upgrade @agenticmail/api to **0.9.64** or later.
If unsure, ask your IT team or search "@agenticmail/api GHSA-hjwc-26pj-v3pm" on the vendor's site.
GHSA-hjwc-26pj-v3pm (@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` without authentication.
📍 Affected scope
@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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@agenticmail/api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@agenticmail/api` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt 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 があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade @agenticmail/api to 0.9.64ステージング環境で 0.9.64 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /api/agenticmail/tasks/pending on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@agenticmail/api
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.64"}]}]