Security Digest · Vulnerability record
CVE-2026-35615: PraisonAI Has Path Traversal in FileTools
PraisonAI is a multi-agent teams system. Prior to 1.5.113, validatepath() calls os.path.normpath() first, which collapses ..
CVSS 9.2 Critical EPSS 0.5% · p45
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.5%, percentile 45: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 45% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
PraisonAI(PyPI) <= 1.5.112, fixed in 1.5.113. Check your lockfile, including transitive dependencies.
What it is
PraisonAI is a multi-agent teams system. Prior to 1.5.113, validatepath() calls os.path.normpath() first, which collapses .. sequences, then checks for '..' in normalized. Since .. is already collapsed, the check always passes. This makes the check completely useless and allows trivial path traversal to any file on the system. This vulnerability is fixed in 1.5.113.
From the GitHub advisory
Executive Summary: The path validation has a critical logic bug: it checks for .. AFTER normpath() has already collapsed all .. sequences. This makes the check completely useless and allows trivial path traversal to any file on the system. The path validation function also does not resolve the symlink wich could potentially cause path traversal.
Details: validatepath() calls os.path.normpath() first, which collapses .. sequences, then checks for '..' in normalized. Since .. is already collapsed, the check always passes.
Vulnerable File: src/praisonai-agents/praisonaiagents/tools/filetools.py
Lines: 42-49
Severity: CRITICAL
Weakness type: CWE-22.
Product: PraisonAI (PyPI) · Assigned by: GitHub_M · Published: 2026-04-07
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | PraisonAI | <= 1.5.112 | 1.5.113 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| MervinPraison | PraisonAI | < 4.5.113 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 4.0 | 9.2 Critical | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N |
| GitHub | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 0.54% probability of exploitation activity in the next 30 days; percentile 45.
Timeline
- — GitHub-reviewed advisory GHSA-693f-pf34-72c5 published (critical)
- — CVE record published by GitHub_M
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-693f-pf34-72c5 github.com
- CVE.org record CVE-2026-35615 cve.org
- NVD entry CVE-2026-35615 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com