Vulnerability in aegra-api (CVE-2026-44504)
Summary
Vulnerability in aegra-api (CVE-2026-44504). Risk of unauthorized operations or information disclosure. Exploitable via POST /threads/{thread_id}/runs. Mitigation: upgrade to 0.9.7 or later.
Original description
The description as published by the source.
Aegra is a drop-in replacement for LangSmith Deployments. Prior to 0.9.7, with multiple authenticated users on a shared instance are vulnerable to a cross-tenant IDOR. Any authenticated attacker, given another user's thread_id, can execute graph runs against the user's thread, read the user's full checkpoint state, and inject arbitrary messages into the user's conversation history. This vulnerability is fixed in 0.9.7.
Source: NIST National Vulnerability Database 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-44504 has been found in aegra-api.
Attackers can target a specific entry point like POST /threads/{thread_id}/runs over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade aegra-api to 0.9.7 or later.
If unsure, ask your IT team or search "aegra-api CVE-2026-44504" on the vendor's site.
CVE-2026-44504 (aegra-api) — CWE-285
Attack surface: POST /threads/{thread_id}/runs / POST /threads/{thread_id}/runs/stream / POST /threads/{thread_id}/runs/wait / GET /threads/{thread_id}/runs
Patched: 0.9.7 — 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-285) exists in aegra-api. Attackers reach the vulnerable code path via POST /threads/{thread_id}/runs.
Check the vendor advisory for the affected versions of aegra-api. Attack surface: POST /threads/{thread_id}/runs / POST /threads/{thread_id}/runs/stream / POST /threads/{thread_id}/runs/wait / GET /threads/{thread_id}/runs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.9.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /threads/{thread_id}/runs requests with malformed payloads or SQL meta-characters. Run grep -r 'aegra-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
-
1Identify exposure identify
grep -r 'aegra-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
aegra-apiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /threads/{thread_id}/runs' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /threads/{thread_id}/runsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade aegra-api to 0.9.7ステージング環境で 0.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /threads/{thread_id}/runs on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
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