PraisonAI: Jobs webhook SSRF protection bypass via DNS rebinding
Impact
PraisonAI versions 4.5.126 to 4.6.59 are vulnerable to a Server-Side Request Forgery (SSRF) protection bypass via DNS rebinding, allowing an attacker to resolve an attacker-controlled hostname to a private target. The weakness is due to a Time-of-check Time-of-use (TOCTOU) Race Condition. An attacker with control over a hostname can exploit this vulnerability.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
MervinPraison · GitHub_M
PraisonAI
1 range
MervinPraison · GitHub_M
PraisonAI
Compare with this publisher’s ranges. This does not inspect your installation.
affected
>= 4.5.126, < 4.6.59
Other versions: unknown
Original source description
PraisonAI is a multi-agent teams system. From version 4.5.126 to before version 4.6.59, PraisonAI's Async Jobs API validates webhook_url when a job request is parsed and again when the internal Job object is constructed. That validation blocks direct loopback/private targets, but it is not bound to the later network request. When a job completes, _send_webhook() passes the original hostname to httpx.AsyncClient.post() with no send-time validation, IP pinning, or guarded transport. An attacker-controlled hostname can therefore resolve to a public IP during Pydantic validation and later resolve to loopback/private/cloud-metadata infrastructure during webhook delivery. This bypasses the intended SSRF guard in current supported releases. This appears to be an incomplete fix / patch bypass for GHSA-8frj-8q3m-xhgm. This issue has been patched in version 4.6.59.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-57114View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.