← Back
CVE-2026-24780
Vulnerability in agpt (CVE-2026-24780)
Summary
vulnerability in agpt (CVE-2026-24780). Risk of unauthorized operations or information disclosure. Exploitable via `POST /api-keys`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-24780** has been found in agpt.
Attackers can target a specific entry point like `POST /api-keys` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "agpt CVE-2026-24780" on the vendor's site.
CVE-2026-24780 (agpt) — CWE-276 /
Attack surface: POST /api-keys / POST /external-api/v1/blocks/{id}/execute / `disabled` / `BlockInstallationBlock`
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-276) exists in agpt. Attackers reach the vulnerable code path via `POST /api-keys` without authentication.
📍 Affected scope
agpt — . Attack surface: POST /api-keys / POST /external-api/v1/blocks/{id}/execute / `disabled` / `BlockInstallationBlock`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 `POST /api-keys` requests with malformed payloads or SQL meta-characters. Run `grep -r 'agpt' .` 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 'agpt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `agpt` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api-keys' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api-keys` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /api-keys on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
agpt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.2.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-24780
- advisory https://github.com/advisories/GHSA-r277-3xc5-c79v
- package https://github.com/Significant-Gravitas/AutoGPT
- package https://pypi.org/project/agpt
- web https://github.com/Significant-Gravitas/AutoGPT/security/advisories/GHSA-r277-3xc5-c79v
- web https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/backend/backend/api/external/v1/routes.py#L79-L93
- web https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/backend/backend/api/features/v1.py#L1408-L1424
- web https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/backend/backend/api/features/v1.py#L355-L395
- web https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/backend/backend/blocks/block.py#L15-L78
- web https://github.com/Significant-Gravitas/AutoGPT/blob/master/autogpt_platform/backend/backend/data/block.py#L459