PraisonAI file-tool bridging flaw in compute-provider agents (EUVD-2026-108902)
- Status
- Unverified: only social posts report this so far
- Kind
- Vulnerability
- Vendor
- mervinpraison
- Product
- PraisonAI
- First seen
Summary
The EUVD listing, scored 8.8 under CVSS v3.1, describes a flaw in PraisonAI versions 4.6.10 up to 4.6.59 in how file tools are bridged for managed and sandboxed agents when a compute provider is attached. The excerpt is truncated and does not state the full impact.
If you use mervinpraison
Upgrade PraisonAI to version 4.6.59 or later
Review agents that use a compute provider with file tools
Read the full EUVD entry for impact details
Disable Discord-based approval for dangerous tool calls until patched
Review recent approved tool calls in Discord channels
Upgrade PraisonAI to version 4.6.61 or later
What the sources say 4
· Mastodon: “From version 4.5.112 to before version 4.6.59, PraisonAI's installed console entrypoint is Typer-first.” Source
· Mastodon: “From version 4.5.115 to before version 4.6.61, the published A2U advisory GHSA-f292-66h9-fpmf says unauthenticated A2U event streaming was fixed in praisonai 4.5.115. Current head sti...” Source
· Mastodon: “From version 4.5.2 to before version 4.6.59, praisonai.bots.DiscordApproval approves a pending dangerous tool call when it sees any later non-bot message in the configured Discord cha...” Source
· Mastodon: “From version 4.6.10 to before version 4.6.59, LocalManagedAgent / SandboxedAgent compute bridging wraps read_file, list_files, and write_file when a compute provider is attached.” Source