Path Traversal in agixt (CVE-2026-39981)
Summary
Path traversal in agixt (CVE-2026-39981). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.9.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-39981 has been found in agixt.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade agixt to 1.9.2 or later.
If unsure, ask your IT team or search "agixt CVE-2026-39981" on the vendor's site.
CVE-2026-39981 (agixt) — CWE-22 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.9.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in agixt.
Check the vendor advisory for the affected versions of agixt.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.9.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'agixt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'agixt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
agixtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade agixt to 1.9.2ステージング環境で 1.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com