Vulnerability in praisonaiagents (CVE-2026-55524)
Summary
Vulnerability in praisonaiagents (CVE-2026-55524). Confidential information can be exposed externally. Mitigation: upgrade to 1.6.58 or later.
Original description
The description as published by the source.
The web_crawl tool performs its SSRF check only on the initial URL: it resolves the hostname once
with socket.gethostbyname and rejects private/loopback/link-local results. It then passes the URL to
a fetcher that uses httpx.Client(follow_redirects=True) - or urllib.request.urlopen when httpx is
absent, which also follows redirects - and re-resolves the hostname at connect time, with no further
validation. This validate-here/fetch-there gap is bypassable two independent ways: HTTP redirects and
DNS rebinding.
Affected code: src/praisonai-agents/praisonaiagents/tools/web_crawl_tools.py
- Single-shot validation (lines 229-238):
if os.environ.get("ALLOW_LOCAL_CRAWL") != "true":
ip_str = socket.gethostbyname(hostname) # resolved ONCE, at validation time
ip = ipaddress.ip_address(ip_str)
if ip.is_loopback or ip.is_private or ip.is_link_local or ip.is_multicast or ip.is_unspecified:
continue # rejected
url_list.append(u) - Vulnerable fetch (_crawl_with_httpx, lines 142 / 149): follows redirects, re-resolves DNS, no re-check:
with httpx.Client(follow_redirects=True, timeout=30.0) as client: response = client.get(url)fallback: urllib.request.urlopen(url, timeout=30) (also follows redirects by default)
- web_crawl / crawl_web are registered tools (tools/init.py:156-157); httpx is the default fallback
provider (dispatch at web_crawl_tools.py:269).
The two bypasses:
- Redire…
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-55524 has been found in praisonaiagents.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade praisonaiagents to 1.6.58 or later.
If unsure, ask your IT team or search "praisonaiagents CVE-2026-55524" on the vendor's site.
CVE-2026-55524 (praisonaiagents) — CWE-367 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
A vulnerability (CWE-367) exists in praisonaiagents.
Check the vendor advisory for the affected versions of praisonaiagents.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
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