Skip to main content
VulnerabilityPublished

CVE-2025-35028: 0x4m4 HexStrike AI · OS Command Injection

Affects 0x4m4 HexStrike AISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 17 Nov 2026, 20:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
5.4% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

AI-suggested

  1. Monitor 0x4m4 vendor communications closely for official patches or updates addressing CVE-2025-35028 and apply them immediately upon release.
  2. Until patches are available, restrict network access to the HexStrike AI MCP server’s API endpoints using firewalls or network segmentation to limit exposure to trusted hosts only.
  3. Implement Web Application Firewall (WAF) rules or intrusion prevention systems (IPS) to detect and block command injection patterns, particularly inputs starting with semicolons or other shell metacharacters.
  4. Employ strict input validation and sanitization at the application layer to reject or safely handle special characters in command-line arguments.
  5. Run the MCP server with the least privilege necessary, avoiding root-level execution where possible, to minimize the impact of potential exploitation.
  6. Conduct regular security audits and penetration testing focused on injection vulnerabilities in AI platforms.
  7. Establish comprehensive logging and monitoring to detect anomalous command execution or API usage patterns indicative of exploitation attempts.
  8. Educate development and operations teams about secure coding practices related to command execution and input handling in AI systems.

Description

By providing a command-line argument starting with a semi-colon ; to an API endpoint created by the EnhancedCommandExecutor class of the HexStrike AI MCP server, the resultant composed command is executed directly in the context of the MCP server’s normal privilege; typically, this is root. There is no attempt to sanitize these arguments in the default configuration of this MCP server at the affected version (as of commit 2f3a5512 in September of 2025).

References

Community reviews

Loading reviews…