# CVE-2026-90619: 0x4m4 HexStrike AI Execute Endpoint hexstrike_server.py os command injection

> Remote attackers can execute arbitrary OS commands via the Execute Endpoint in HexStrike AI due to improper input validation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-crrg-2r24-3g67

## What is CVE-2026-90619?

CVE-2026-90619 is a medium-severity command injection vulnerability in 0x4m4 HexStrike AI, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in 0x4m4 HexStrike AI up to d689933ff579d839c676c82b231f8e98326c5f04. Impacted is an unknown function of the file hexstrike_server.py of the component Execute Endpoint. The manipulation of the argument code/script leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

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

## Which versions are affected by CVE-2026-90619?


## How do I fix CVE-2026-90619?

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

## Is CVE-2026-90619 being exploited?

There is no known exploitation of CVE-2026-90619 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90619 and fix it if it is affected.

What it is: CVE-2026-90619 is a medium-severity command injection vulnerability in 0x4m4 HexStrike AI, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90619 in the wild and no public exploit code.

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-2026-90619/ (Markdown: https://insights.sbomify.com/CVE-2026-90619/index.md)
```

## Sources

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

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