AGiXT hat eine Path Traversal in safe_join()

The vulnerability lies within the safejoin() function of the essentialabilities extension, which fails to properly validate file paths. An attacker, after authentication, can craft directory traversal sequences (e.g., ../..) to navigate outside the intended agent workspace. This allows them to read sensitive configuration files, modify application data, or even delete critical system files. The potential impact extends to complete compromise of the AGiXT instance and potentially the underlying server, depending on the permissions of the AGiXT user account. While requiring authentication, the ease of exploitation makes this a significant risk, especially in environments with weak password policies or compromised user accounts.

Organizations deploying AGiXT in production environments, particularly those with limited access controls or inadequate monitoring, are at significant risk. Shared hosting environments where multiple AGiXT instances reside on the same server are also vulnerable, as a compromise of one instance could potentially lead to the compromise of others.

• nodejs: Monitor AGiXT logs for unusual file access patterns or attempts to access files outside the designated workspace. Use lsof to identify processes accessing files within the workspace.

lsof /path/to/agixt/workspace

• generic web: Examine access logs for requests containing directory traversal sequences (e.g., ../..).

grep '../..' /var/log/apache2/access.log

• generic web: Check response headers for unexpected file content or server errors related to file access.

1. 2026-04-09Disclosure

   disclosure

1. Reserviert2026-04-08
2. Veröffentlicht2026-04-09
3. Geändert2026-04-13
4. EPSS aktualisiert2026-04-17

The primary mitigation is to immediately upgrade AGiXT to version 1.9.2 or later, which includes the necessary fix for the safe_join() function. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) rule to block requests containing directory traversal sequences like ../. Additionally, restrict the permissions of the AGiXT user account to the minimum required for its operation, limiting the potential damage from a successful exploit. Regularly review and audit file system access logs for suspicious activity. After upgrading, confirm the fix by attempting a directory traversal attack and verifying that access is denied.