CVE-2026-39981: Josh-XT AGiXT · Path Traversal
Affects Josh-XT AGiXTSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 1.9.2 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade AGiXT and josh-xt/AGiXT to 1.9.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Josh-XTAGiXT | Affected
| Fixed in
|
GitHubjosh-xt/AGiXTpkg:github/josh-xt/AGiXTOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade AGiXT to version 1.9.2 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 1.9.2, applying this official update is the recommended remediation. No other mitigation steps are specified or required.
Description
AGiXT is a dynamic AI Agent Automation Platform. Prior to 1.9.2, the safe_join() function in the essential_abilities extension fails to validate that resolved file paths remain within the designated agent workspace. An authenticated attacker can use directory traversal sequences to read, write, or delete arbitrary files on the server hosting the AGiXT instance. This vulnerability is fixed in 1.9.2.