← Back
CVE-2026-40160

SSRF (Server-Side Request Forgery) in praisonaiagents (CVE-2026-40160)

Summary

SSRF in praisonaiagents (CVE-2026-40160). Risk of unauthorized operations or information disclosure. Exploitable via ``web_crawl``. Mitigation: upgrade to `1.5.128` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-40160** has been found in praisonaiagents. Attackers can target a specific entry point like ``web_crawl`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade praisonaiagents to **1.5.128** or later. If unsure, ask your IT team or search "praisonaiagents CVE-2026-40160" on the vendor's site.
CVE-2026-40160 (praisonaiagents) — CWE-918 / Attack surface: `web_crawl` / `download_file` / `TAVILY_API_KEY` / `crawl4ai` Patched: `1.5.128` — 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
**SSRF** (CWE-918) exists in praisonaiagents. Attackers reach the vulnerable code path via ``web_crawl`` without authentication.
📍 Affected scope
praisonaiagents — . Attack surface: `web_crawl` / `download_file` / `TAVILY_API_KEY` / `crawl4ai`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.5.128**.
🛡️ 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 'praisonaiagents' .` 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

  1. 1
    Identify exposure identify
    grep -r 'praisonaiagents' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade praisonaiagents to 1.5.128

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

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

PyPI praisonaiagents
[{"type":"ECOSYSTEM","events":[{"introduced":"0.13.23"},{"fixed":"1.5.128"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →