PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, the Jobs API validate_webhook_url() path fails open on socket.gaierror and does not bind the validated address to the later request. An attacker webhook_url can later resolve to 127.0.0.1, 169.254.169.254, or another internal address. This issue is fixed in version 4.6.58.
CVE-2026-55535
This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(medium)
- EG Risk
- 47(Track)EG Risk 47/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity68% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026Server-Side Request Forgery via DNS rebinding bypass in webhook_url validation in PraisonAI · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-hmfx-4v44-9qw9PraisonAI v4.6.58
Patch available: MervinPraison/PraisonAI v4.6.58
https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58commit 2f9677abb2ea (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.137 (contains commit 2f9677abb2ea)
https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1Vendor Advisories for CVE-2026-55535(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonai | 0.0.1 ... 4.6.9 (748 versions) | 4.6.58 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 12:33 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 16:00 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:46 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 19:22 UTCEG score recompute
- 2026-08-25 18:31 UTCEG score recompute
- 2026-08-25 15:21 UTCEG score recompute
- 2026-08-25 15:15 UTCEG score recompute
- 2026-08-25 15:14 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-55535?
When was CVE-2026-55535 disclosed?
Is CVE-2026-55535 actively exploited?
What is the CVSS score of CVE-2026-55535?
How do I remediate CVE-2026-55535?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55535
Is Your Infrastructure Affected by CVE-2026-55535?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.