GHSA-p4pj-vh7h-6cqh
HIGHGHSA-p4pj-vh7h-6cqh is a high-severity (CVSS 7.5) Path Traversal vulnerability in praisonai. O3 Security confirms whether GHSA-p4pj-vh7h-6cqh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
PraisonAI: Unauthenticated Local File Inclusion via agent_file path in PraisonAI Jobs API
Real-World Exposure
praisonaiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An unauthenticated attacker can read arbitrary files on the server by supplying an absolute filesystem path in the agent_file field of the Jobs API. The field has no path validation, no allowlist, and no authentication is required to submit jobs.
Details
The agent_file field in JobSubmitRequest accepts any filesystem path with no validation:
# src/praisonai/praisonai/jobs/models.py:29
agent_file: Optional[str] = Field(None, description="Path to agents.yaml file")
# NO path validator, NO allowlist
The executor reads the file directly:
# src/praisonai/praisonai/jobs/executor.py:221
agent_file = job.agent_file or "agents.yaml"
# passed directly to yaml.safe_load(open(agent_file))
Proof of Concept
curl -X POST http://:8005/api/v1/runs \
-H "Content-Type: application/json" \
-d '{"prompt": "run", "agent_file": "/etc/passwd"}'
Server responds with contents of /etc/passwd.
Other exploitable paths:
/proc/1/environ— environment variables, API keys/home//.ssh/id_rsa— SSH private keys/app/.env— application secrets
Impact
Any unauthenticated attacker with network access to port 8005 can read any file accessible to the server process, including credentials, private keys, and environment variables.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | praisonai | all versions | 4.6.59 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for praisonai. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update praisonai to 4.6.59 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p4pj-vh7h-6cqh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-p4pj-vh7h-6cqh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-p4pj-vh7h-6cqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p4pj-vh7h-6cqh in your dependencies?
O3 detects GHSA-p4pj-vh7h-6cqh across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.