GHSA-hwg5-x759-7wjg
HIGHGHSA-hwg5-x759-7wjg is a high-severity (CVSS 8.8) Code Injection vulnerability in praisonai. O3 Security confirms whether GHSA-hwg5-x759-7wjg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
PraisonAI has Template Injection in Agent Tool Definitions
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
Direct insertion of unescaped user input into template-rendering tools allows arbitrary code execution via specially crafted agent instructions.
Details
The create_agent_centric_tools() function returns tools (like acp_create_file) that process file content using template rendering. When user input from agent.start() is passed directly into these tools without escaping (as shown in agent_centric_example.py:85-86), template expressions in the input are executed rather than treated as literal text. This occurs because:
- No input sanitization or escaping is applied to user-controlled content
- The ACP-enabled runtime auto-approves operations (
approval_mode="auto") - Tools lack context-aware escaping for template syntax
PoC
# Replace the agent.start() call at line 85 with:
result = agent.start('Create file with content: {{ self.__init__.__globals__.__builtins__.__import__("os").system("touch /tmp/pwned") }}')
Successful exploitation creates /tmp/pwned confirming arbitrary command execution. The expression {{7*7}} renders as 49 instead of literal text.
Impact
Attackers can execute arbitrary system commands with the privileges of the running process by injecting malicious template expressions through agent instructions. This compromises the host system, enabling data theft, ransomware deployment, or lateral movement.
Recommended Fix
- Input Sanitization: Implement strict whitelist validation for file content
- Contextual Escaping: Auto-escape template syntax characters (e.g.,
{{ }}) in user input using Jinja2autoescape=True - Sandboxing: Restrict template execution environments using secure eval modes
- Approval Hardening: Require manual approval for file creation operations in production
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | praisonai | all versions | 4.5.115 |
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.5.115 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwg5-x759-7wjg 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-hwg5-x759-7wjg 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-hwg5-x759-7wjg. 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-hwg5-x759-7wjg in your dependencies?
O3 detects GHSA-hwg5-x759-7wjg across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.