Description

A weakness has been identified in 0x4m4 HexStrike AI up to d689933ff579d839c676c82b231f8e98326c5f04. The affected element is the function subprocess.Popen of the file hexstrike_server.py of the component API Tools Endpoint. Executing a manipulation of the argument additional_args/target/username/password/scan_type/payload can lead to os command injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. A fix appears to be in progress.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-09-14T07:17:24.880Z",
  "pubdate": "2026-09-14T07:17:24.880Z",
  "executiveSummary": "A critical OS command injection vulnerability exists within the 0x4m4 HexStrike AI API Tools Endpoint component, specifically affecting versions up to d689933ff579d839c676c82b231f8e98326c5f04.\nThe vulnerability originates from the improper sanitization of user-supplied input passed to the subprocess.Popen function within hexstrike_server.py.\nSuccessful exploitation allows a remote, unauthenticated attacker to execute arbitrary OS commands on the underlying host with the privileges of the application process.\nGiven that public exploit code is available, this vulnerability poses a severe risk to confidentiality, integrity, and availability, potentially leading to full system compromise.\nBecause the product lacks a formal versioning schema, all current deployments should be considered vulnerable unless confirmed otherwise by the pending vendor fix.",
  "technicalDetails": "The vulnerability resides in the hexstrike_server.py script within the API Tools Endpoint component of 0x4m4 HexStrike AI. The root cause is the insecure utilization of the subprocess.Popen function, which is invoked to process various input vectors, including additional_args, target, username, password, scan_type, and payload.\nIn the vulnerable implementation, these parameters are concatenated directly into shell commands or passed to subprocess.Popen without sufficient validation or escaping. When the function is called with shell=True or by passing a single string to the Popen constructor, the Python interpreter invokes the system shell (e.g., /bin/sh or cmd.exe) to execute the command string.\nAn attacker can manipulate the input parameters to inject shell metacharacters such as ';', '&&', '|', or '`'. By crafting a malicious payload, an attacker can break out of the intended command context and execute arbitrary OS commands.\nThe attack flow proceeds as follows: 1) The attacker identifies the API endpoint that processes one of the aforementioned parameters. 2) The attacker submits an HTTP request to the API, injecting a crafted payload into the vulnerable field. 3) The hexstrike_server.py process receives the input and passes it to subprocess.Popen. 4) The underlying shell interprets the injected characters as command separators or operators, subsequently executing the attacker's secondary commands.\nBecause this endpoint is remotely accessible, no authentication or special privileges are required for exploitation. The injected payload is executed with the environment permissions of the user running the HexStrike AI server, which may include full read/write access to the filesystem, network access, or the ability to spawn reverse shells.\nPost-exploitation impact includes unauthorized data exfiltration, modification of system configurations, or lateral movement within the network. The existence of public exploit code significantly lowers the barrier to entry for adversaries, making immediate remediation essential."
}