PraisonAI: Webhook SSRF via DNS fail-open in JobSubmitRequest.validate_webhook_url() — bypass of CVE-2026-40114

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS

• CVE-2026-55537: 0.27% estimated exploitation activity in the next 30 days; percentile 18.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary praisonai/jobs/models.py::JobSubmitRequest.validatewebhookurl() validates webhook URLs by resolving the hostname and checking whether the IP is private. When DNS resolution fails (socket.gaierror), the validator silently passes the URL via except socket.gaierror: pass. Additionally, even when DNS succeeds at validation time, the webhook is fired much later by JobExecutor.sendwebhook(), which calls httpx.AsyncClient().post(job.webhookurl) — performing a fresh, independent DNS lookup at execution time. Together, these flaws create a TOCTOU SSRF window. An attacker can: 1. Submit a job with webhookurl pointing to a hostname that currently does not resolve (NXDOMAIN) → validation passes (gaierror → pass) 2. Update DNS to point that hostname to 127.0.0.1 or another private IP 3. When the job completes, sendwebhook() resolves the hostname fresh → POST sent to the internal IP Details Flaw 1 — Fail-open on DNS error (jobs/models.py lines 58-66): When socket.gethostbyname(hostname)…

Published by the source

25 Aug 2026, 14:59 UTC

Last modified by the source

25 Aug 2026, 14:59 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rg5q-pp8p-f7jm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55537

Advisory: PraisonAI: Webhook SSRF via DNS fail-open in `JobSubmitRequest.validate_webhook_url()` — bypass of CVE-2026-40114
IDs: CVE-2026-55537, GHSA-rg5q-pp8p-f7jm
Record: https://patchnext.com/advisories/cve-2026-55537 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.6.58. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected < 4.6.58; fixed in 4.6.58

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rg5q-pp8p-f7jm (GitHub-reviewed advisory GHSA-rg5q-pp8p-f7jm lists affected ranges: PyPI praisonai >=0 <4.6.58)

Commands are suggestions: review each one before running it.