CVE-2026-55524: MervinPraison PraisonAI · Time-of-check Time-of-use (TOCTOU) Race Condition
Affects MervinPraison PraisonAISource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.6.58 soon.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.6.58
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade PraisonAI and mervinpraison/PraisonAI to 1.6.58.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MervinPraisonPraisonAI | Affected
| Fixed in
|
GitHubmervinpraison/PraisonAIpkg:github/mervinpraison/PraisonAIOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in PraisonAI version 1.6.58. Users should upgrade to version 1.6.58 or later to remediate the issue. No other vendor advisories or temporary mitigations are provided. Patch status is not explicitly stated but the fix version is known, so upgrading is the recommended remediation.
Description
PraisonAI versions prior to 1.6.58 contain a time-of-check to time-of-use (TOCTOU) race condition in the web_crawl tool's SSRF protection. The tool validates the initial URL's hostname against private, loopback, and link-local addresses only once, but then follows redirects and re-resolves hostnames without revalidating. This allows attackers to bypass SSRF protections via HTTP redirects or DNS rebinding, potentially causing the host to fetch internal or cloud metadata endpoints and expose sensitive data. The issue is fixed in version 1.6.58.