Quick answers
- Is CVE-2026-76832 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76832 being exploited in the wild.
- How severe is CVE-2026-76832?
- High severity, with a CVSS score of 8.8, published 19 August 2026.
- Which products and versions are affected?
- Agno PythonTools prior to 2026-01-07.
- Is there a fix for CVE-2026-76832?
- A patch was published on 2026-01-07: Fix implemented in commit 710d7e7 adding restrict_to_base_dir parameter Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76832 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76832?
- Check whether you run Agno PythonTools at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic path traversal flaw in the PythonTools file handling functions (read_file, save_to_file, run_python_file) located in libs/agno/agno/tools/python.py. The root cause is insufficient validation of user-supplied file_name arguments; attackers can inject sequences like '../../../../../../etc/passwd' to escape the intended base_dir boundary. The flaw can be exploited directly via tool invocation or indirectly through prompt injection in agent-processed content. An unauthenticated attacker with network access can read arbitrary files, write files outside the restricted directory, or execute arbitrary Python code within the process's user authority. A fix adding a restrict_to_base_dir parameter was implemented in commit 710d7e7 (2026-01-07).
Affected products
- Agno PythonTools prior to 2026-01-07
Timeline
- 2026-08-19: disclosed: CVE-2026-76832 published
- 2026-01-07: patched: Fix implemented in commit 710d7e7 adding restrict_to_base_dir parameter