A critical path traversal vulnerability in HexStrike AI allows unauthenticated attackers to achieve remote code execution through arbitrary file writes.

The application fails to validate the filename argument within the FileOperationsManager function in hexstrike_server.py. This flaw enables unauthenticated remote attackers to bypass directory restrictions via path traversal sequences, leading to arbitrary file creation on the server.

Successful exploitation allows an attacker to write files anywhere on the filesystem accessible by the application process. This can lead to full system compromise through the injection of malicious web shells, unauthorized modification of system configurations, or the overwriting of critical binaries. Given the CVSS score of 8.3, this high-severity vulnerability poses a substantial risk of data breach and persistent unauthorized access to the environment.

Immediate Action: As no official patch is currently available, administrators should restrict network access to the API Files Endpoint to trusted sources only. If possible, implement the validation logic suggested in the research write-up to verify that the resolved file path remains within the designated base directory.

Proactive Monitoring: Review web server and application logs for suspicious POST requests to the /api/files/create endpoint containing directory traversal sequences such as dot-dot-slash patterns.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block path traversal attempts and suspicious file extensions in API requests.

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the GitHub issue report (https://github.com/0x4m4/hexstrike-ai/issues/135).

Due to the lack of an official patch and the availability of a public exploit, this vulnerability presents an urgent risk to organizational security. Administrators must prioritize isolating the affected component and implementing robust input validation to prevent unauthorized file writes. Monitor the project repository closely for an official security update and apply it immediately upon release.