SSRF (Server-Side Request Forgery) in praisonaiagents (CVE-2026-55523)
Summary
SSRF in praisonaiagents (CVE-2026-55523). Risk of unauthorized operations or information disclosure. Exploitable via web_crawl. Mitigation: upgrade to 1.6.58 or later.
Original description
The description as published by the source.
Summary
praisonaiagents.tools.web_crawl_tools.web_crawl() validates the initial URL and blocks direct loopback/private destinations by default, but the default httpx fallback still uses httpx.Client(follow_redirects=True) and does not revalidate redirect targets.
An attacker-controlled public URL can pass the initial host check, redirect to loopback/private/cloud metadata infrastructure, and have the redirected response body returned by web_crawl().
This appears to be an incomplete fix / patch bypass for the published web_crawl SSRF class (GHSA-qq9r-63f6-v542 / CVE-2026-40160, and GHSA-8f4v-xfm9-3244).
Affected Component
Package:
praisonaiagents
File:
src/praisonai-agents/praisonaiagents/tools/web_crawl_tools.py
Functions:
web_crawl()
_crawl_with_httpx()
Affected Versions
Validated affected:
praisonaiagents 1.5.128via repository tagv4.5.128;praisonaiagents 1.6.40via repository tagv4.6.40;praisonaiagents 1.6.56via repository tagv4.6.56;- current
origin/maincommit095653d78a01cc6c80ff5b2dd20a8e5619686ddc.
Suggested affected range for maintainer confirmation:
>= 1.5.128, <= 1.6.56
No patched version is known to me at submission time.
Root Cause
Current web_crawl() validates only the initially supplied URL:
- requires
httporhttps; - resolves the initial hostname with
socket.gethostbyname(); - rejects loopback/private/link-local/multicast/unspecifi…
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-55523 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.6.58 or later.
If unsure, ask your IT team or search "praisonaiagents CVE-2026-55523" on the vendor's site.
CVE-2026-55523 (praisonaiagents) — CWE-918
Attack surface: web_crawl / http / https / httpx
Patched: 1.6.58 — 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 / http / https / httpx.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.6.58.
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.6.58ステージング環境で 1.6.58 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com