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.
Original description
The description as published by the source.
| Field | Value |
|---|---|
| Severity | High |
| Type | SSRF -- unvalidated URL in web_crawl httpx fallback allows internal network access |
| Affected | src/praisonai-agents/praisonaiagents/tools/web_crawl_tools.py:133-180 |
Summary
web_crawl's httpx fallback path passes user-supplied URLs directly to httpx.AsyncClient.get() with follow_redirects=True and no host validation. An LLM agent tricked into crawling an internal URL can reach cloud metadata endpoints (169.254.169.254), internal services, and localhost. The response content is returned to the agent and may appear in output visible to the attacker.
This fallback is the default crawl path on a fresh PraisonAI installation (no Tavily key, no Crawl4AI installed).
Details
The vulnerable code is in tools/web_crawl_tools.py:148-155:
async with httpx.AsyncClient(
follow_redirects=True,
timeout=httpx.Timeout(30)
) as client:
response = await client.get(url) # url from agent tool call, no validation
No scheme restriction, no hostname resolution, no private/link-local IP check. follow_redirects=True also means an attacker can use an open redirect on a public URL to bounce the request into internal networks.
download_file in file_tools.py:295-318, by contrast, validates URLs before requesting:
parsed = urllib.parse.urlsplit(url)
if parsed.scheme not in ("http", "https"):
return "Error: Only HTTP(S) URLs are allowed"
hostname = parsed.hostname
addr = ipa…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-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.
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.
SSRF (CWE-918) exists in praisonaiagents. Attackers reach the vulnerable code path via web_crawl.
Check the vendor advisory for the affected versions of praisonaiagents. Attack surface: web_crawl / download_file / TAVILY_API_KEY / crawl4ai.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.128.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'praisonaiagents' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonaiagentsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonaiagents to 1.5.128ステージング環境で 1.5.128 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com