CVE-2026-90619

7.3

0x4m4 · HexStrike AI

HexStrike AI contains an unauthenticated OS command injection vulnerability in the /api/python/execute endpoint, allowing remote attackers to execute arbitrary code via the code or script arguments.

Executive summary

A critical unauthenticated remote code execution vulnerability in HexStrike AI allows attackers to run arbitrary Python scripts, posing a total system compromise risk.

Vulnerability

This is an OS command injection flaw (CWE-78) located in the hexstrike_server.py file. The application accepts unauthenticated POST requests at the /api/python/execute endpoint, which writes user-supplied input to a temporary file and executes it via a subprocess without any validation or sandboxing.

Business impact

Successful exploitation grants an attacker the ability to execute arbitrary commands with the privileges of the HexStrike server process. This can lead to full system compromise, unauthorized access to sensitive data, and the potential for lateral movement within the network. Given the CVSS score of 7.3 and the nature of remote command execution, this vulnerability represents a high risk to organizational data integrity and availability.

Remediation

Immediate Action: As no official patch is available, immediately disable or restrict access to the /api/python/execute endpoint via network security controls. If the functionality is not strictly required, remove the endpoint from the source code entirely.

Proactive Monitoring: Monitor server logs for POST requests directed to /api/python/execute and inspect the filesystem for suspicious temporary .py files. Look for anomalous subprocess invocations originating from the Python interpreter.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to block POST requests to the vulnerable API path. If the service must remain online, isolate the application within a hardened container with restricted network access and a read-only filesystem.

Exploitation status

Public Exploit Available: Yes, a functional proof-of-concept exists as documented in the GitHub issue report provided by the researcher.

Analyst recommendation

Due to the severity of this remote code execution flaw and the lack of a vendor-provided patch, users must treat this as an urgent security priority. Until the developer provides an update, the most effective mitigation is to isolate the server from public access and disable the vulnerable endpoint to prevent unauthorized code execution.

More 0x4m4 CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by ez-lbz (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.