# CVE-2026-90691: 0x4m4 HexStrike AI API Files Endpoint hexstrike_server.py FileOperationsManager path traversal

> Remote attackers can exploit a path traversal flaw in the HexStrike AI API to read or modify arbitrary files on the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/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:** 14 Sep 2026
- **Also known as:** GHSA-qr7w-g3j4-2vq2

## What is CVE-2026-90691?

CVE-2026-90691 is a medium-severity path traversal 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 security vulnerability has been detected in 0x4m4 HexStrike AI up to d689933ff579d839c676c82b231f8e98326c5f04. The impacted element is the function FileOperationsManager of the file hexstrike_server.py of the component API Files Endpoint. The manipulation of the argument filename leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-90691 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90691 is a medium-severity path traversal 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90691 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-2026-90691/ (Markdown: https://insights.sbomify.com/CVE-2026-90691/index.md)
```

## Sources

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

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