# CVE-2025-35028: HexStrike AI MCP Server Command Injection

> Attackers can execute arbitrary commands with root privileges by injecting semi-colons into API arguments in the HexStrike AI MCP server.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-2j8m-rmq4-rcw5

## What is CVE-2025-35028?

CVE-2025-35028 is a critical command injection vulnerability in 0x4m4 HexStrike AI, published on 30 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-35028?


## How do I fix CVE-2025-35028?

No fix has been published for CVE-2025-35028 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-35028 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-35028 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-35028 and fix it if it is affected.

What it is: CVE-2025-35028 is a critical command injection vulnerability in 0x4m4 HexStrike AI, published on 30 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-35028 exists.

Affected product: 0x4m4 HexStrike AI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-35028/ (Markdown: https://insights.sbomify.com/CVE-2025-35028/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-35028
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-35028
- OSV: https://osv.dev/vulnerability/CVE-2025-35028

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-35028/
Summaries are generated and may contain mistakes; the official description above is the record.