CVE-2026-55527

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, the FileMemory constructor joins unsanitized user_id into self.user_path. A caller supplying ../ or path separators can escape the memory directory and write JSON data to arbitrary process-writable locations. The fix sanitizes user_id before constructing self.user_path. This issue is fixed in version 1.6.58.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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 computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Arbitrary file write via unsanitized `user_id` in `FileMemory.__init__()` — path traversal to any writable location · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-gxmw-5f7x-6g22
github_release Patch Available

PraisonAI v4.6.58

Patch available: MervinPraison/PraisonAI v4.6.58

https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58
github_commit Patch Available

commit 2f9677abb2ea (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.137 (contains commit 2f9677abb2ea)

https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1

Vendor Advisories for CVE-2026-55527(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)
PackageVulnerable rangeFix by version rangeDependents
praisonaiagents0.0.1 ... 1.6.9 (585 versions)
  • every version up to 1.6.58: fixed in 1.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 / 54× 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.

  1. 2026-10-10 12:03 UTCEG score recompute
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-09 04:23 UTCEG score recompute
  4. 2026-10-08 17:12 UTCEPSS rescore
  5. 2026-10-08 03:18 UTCEG score recompute
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-07 01:10 UTCEG score recompute
  8. 2026-10-06 15:18 UTCEPSS rescore
  9. 2026-10-06 02:33 UTCEG score recompute
  10. 2026-10-05 17:43 UTCEPSS rescore
  11. 2026-10-05 02:21 UTCEG score recompute
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-03 16:41 UTCEG score recompute
  14. 2026-10-03 14:26 UTCEPSS rescore
  15. 2026-10-02 18:23 UTCEG score recompute
  16. 2026-10-02 17:56 UTCEPSS rescore
  17. 2026-10-01 20:06 UTCEG score recompute
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-09-30 20:15 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescore
  21. 2026-09-30 06:48 UTCEG score recompute
  22. 2026-09-29 15:22 UTCEPSS rescore
  23. 2026-09-29 08:38 UTCEG score recompute
  24. 2026-09-28 21:30 UTCEG score recompute
  25. 2026-09-28 13:51 UTCEPSS rescore
Show 57 more
  1. 2026-09-27 20:40 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescore
  3. 2026-09-26 22:05 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescore
  5. 2026-09-24 22:15 UTCEG score recompute
  6. 2026-09-24 14:04 UTCEPSS rescore
  7. 2026-09-23 23:27 UTCEG score recompute
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 00:42 UTCEG score recompute
  10. 2026-09-22 02:25 UTCEG score recompute
  11. 2026-09-21 03:44 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-19 18:17 UTCEG score recompute
  14. 2026-09-18 19:33 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 21:09 UTCEG score recompute
  17. 2026-09-17 19:31 UTCEPSS rescore
  18. 2026-09-16 21:34 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 09:33 UTCEG score recompute
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 11:13 UTCEG score recompute
  23. 2026-09-15 03:11 UTCEPSS rescore
  24. 2026-09-14 01:46 UTCEG score recompute
  25. 2026-09-13 16:47 UTCEPSS rescore
  26. 2026-09-12 16:17 UTCEG score recompute
  27. 2026-09-11 17:59 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescore
  29. 2026-09-10 19:41 UTCEG score recompute
  30. 2026-09-10 09:35 UTCEPSS rescore
  31. 2026-09-09 01:14 UTCEG score recompute
  32. 2026-09-08 22:01 UTCEPSS rescore
  33. 2026-09-06 14:07 UTCEG score recompute
  34. 2026-09-06 13:47 UTCEPSS rescore
  35. 2026-09-05 15:49 UTCEG score recompute
  36. 2026-09-04 17:31 UTCEG score recompute
  37. 2026-09-04 06:20 UTCEG score recompute
  38. 2026-09-04 05:06 UTCEPSS rescore
  39. 2026-09-02 20:44 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescore
  41. 2026-09-01 21:32 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescore
  43. 2026-08-31 00:53 UTCEG score recompute
  44. 2026-08-30 19:17 UTCEPSS rescore
  45. 2026-08-30 02:36 UTCEG score recompute
  46. 2026-08-30 01:22 UTCEPSS rescore
  47. 2026-08-29 04:17 UTCEG score recompute
  48. 2026-08-28 21:41 UTCEPSS rescore
  49. 2026-08-27 18:11 UTCEG score recompute
  50. 2026-08-27 14:25 UTCEPSS rescore
  51. 2026-08-26 18:42 UTCEG score recompute
  52. 2026-08-26 14:46 UTCEPSS rescore
  53. 2026-08-25 20:24 UTCEG score recompute
  54. 2026-08-25 19:36 UTCEG score recompute
  55. 2026-08-25 15:21 UTCEG score recompute
  56. 2026-08-25 15:15 UTCEG score recompute
  57. 2026-08-25 15:14 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55527?
CVE-2026-55527 is a high vulnerability published on August 25, 2026. PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, the FileMemory constructor joins unsanitized userid into self.userpath. A caller supplying ../ or path separators can escape the memory directory and write JSON data to arbitrary process-writable locations. The fix sanitizes…
When was CVE-2026-55527 disclosed?
CVE-2026-55527 was first published on August 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55527 actively exploited?
CVE-2026-55527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55527?
CVE-2026-55527 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55527?
A fix for CVE-2026-55527 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55527 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55527

Explore →

Is Your Infrastructure Affected by CVE-2026-55527?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs