SSRF (Server-Side Request Forgery) in praisonaiagents (CVE-2026-40150)
Summary
SSRF in praisonaiagents (CVE-2026-40150). Confidential information can be exposed externally. Exploitable via httpx. Mitigation: upgrade to 1.5.128 or later.
Original description
The description as published by the source.
Summary
The web_crawl() function in praisonaiagents/tools/web_crawl_tools.py accepts arbitrary URLs from AI agents with zero validation. No scheme allowlisting, hostname/IP blocklisting, or private network checks are applied before fetching. This allows an attacker (or prompt injection in crawled content) to force the agent to fetch cloud metadata endpoints, internal services, or local files via file:// URLs.
Details
The web_crawl() function at web_crawl_tools.py:182 accepts a URL string or list of URLs and passes them directly to HTTP clients without any SSRF protections:
# web_crawl_tools.py:182-234
def web_crawl(
urls: Union[str, List[str]],
provider: Optional[str] = None,
) -> Union[Dict[str, Any], List[Dict[str, Any]]]:
# Normalize to list
single_url = isinstance(urls, str)
# ...
url_list = [urls] if single_url else urls
# No URL validation whatsoever — urls flow directly to providers
if selected == "tavily":
results = _crawl_with_tavily(url_list)
elif selected == "crawl4ai":
results = _crawl_with_crawl4ai(url_list)
else:
results = _crawl_with_httpx(url_list) # Always-available fallback
The _crawl_with_httpx() fallback at line 133 makes the actual requests:
# web_crawl_tools.py:140-150
try:
import httpx
with httpx.Client(follow_redirects=True, timeout=30.0) as client:
response = client.get(url) # Line 143: fetches ANY URL, follows re…
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-40150 has been found in praisonaiagents.
Attackers can target a specific entry point like httpx over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade praisonaiagents to 1.5.128 or later.
If unsure, ask your IT team or search "praisonaiagents CVE-2026-40150" on the vendor's site.
CVE-2026-40150 (praisonaiagents) — CWE-918
Attack vector: remote (network-reachable) / no user interaction
Attack surface: httpx / urllib
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 httpx.
Check the vendor advisory for the affected versions of praisonaiagents. Attack surface: httpx / urllib.
Severity: ?. Confidential information can be exposed externally.
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