Description

A security vulnerability has been detected in 0x4m4 HexStrike AI up to d689933ff579d839c676c82b231f8e98326c5f04. The impacted element is the function FileOperationsManager of the file hexstrike_server.py of the component API Files Endpoint. The manipulation of the argument filename leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.3",
  "pubDate": "2026-09-14T07:17:25.080Z",
  "pubdate": "2026-09-14T07:17:25.080Z",
  "executiveSummary": "A path traversal vulnerability has been identified in the 0x4m4 HexStrike AI API Files Endpoint, specifically within the FileOperationsManager function of hexstrike_server.py.\nThe vulnerability affects all versions up to d689933ff579d839c676c82b231f8e98326c5f04.\nThis flaw allows a remote, unauthenticated attacker to manipulate the 'filename' argument to access files and directories outside of the intended web root or application directory.\nThe risk implication is significant, as it enables unauthorized information disclosure of sensitive configuration files, source code, or system credentials.\nPublic disclosure of the exploit code increases the likelihood of active exploitation, particularly given the lack of vendor response to the initial security report.\nOrganizations deploying HexStrike AI should treat this as a critical exposure, as it allows attackers to bypass file system access controls through malicious URI input manipulation.",
  "technicalDetails": "The root cause of this vulnerability is the improper validation and sanitization of user-supplied input in the 'filename' parameter passed to the FileOperationsManager function within hexstrike_server.py.\nThe application fails to effectively neutralize directory traversal sequences—specifically dot-dot-slash ('../') sequences—before passing the input to underlying file system APIs.\nWhen an attacker submits a crafted filename request, the server-side code resolves the path relative to the application's base directory. By injecting traversal sequences, the attacker can break out of the designated directory constraint.\nThe exploitation flow initiates when a remote attacker sends a specially crafted HTTP request to the API endpoint responsible for file handling. The payload typically includes sequences such as '../../' followed by a target sensitive file path (e.g., '/etc/passwd' or application-specific configuration files).\nUpon receiving the request, the FileOperationsManager function processes the malformed filename without validating whether the resolved canonical path resides within the intended, restricted directory. The application then performs an read operation on the resulting path, retrieving the content of the unintended file.\nThe attack is remotely executable and does not require prior authentication, significantly broadening the attack surface. This allows an attacker to probe the file system, potentially exfiltrating environment variables, database credentials, or private keys stored on the host system.\nThe impact is not limited to simple data leakage; an attacker may leverage this vulnerability to map the server's file system structure or gain further insights into the environment to facilitate secondary attacks.\nThe vulnerability is a direct result of the application assuming the trustworthiness of user input in the file access layer, failing to implement essential security controls such as filename normalization, path canonicalization, or the use of chroot-like environments to isolate file operations."
}