Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of praisonaiagents before 1.6.58 let a caller-supplied user_id in FileMemory traverse out of the memory directory, so JSON memory files can be written to any location the process can write to. An attacker who can set user_id, directly through the Python API or indirectly through an Agent memory dict, agents.yaml, or the jobs API, can overwrite files or plant new ones outside the intended base path. Upgrade to praisonaiagents 1.6.58, which fixes the issue; the source gives no other workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0048, the 42nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:10 UTC First seen by agentprime
- 31 Oct 2026, 14:10 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-gxmw-5f7x-6g22
- OSV: GHSA-gxmw-5f7x-6g22
- github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gxmw-5f7x-6g22
- github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1
- github.com/MervinPraison/PraisonAI
- github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58