Quick answers
- Is CVE-2026-90619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90619 being exploited in the wild.
- How severe is CVE-2026-90619?
- High severity, with a CVSS score of 7.3, published 14 September 2026.
- Which products and versions are affected?
- 0x4m4 HexStrike AI up to d689933ff579d839c676c82b231f8e98326c5f04.
- Is there a fix for CVE-2026-90619?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-90619 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-90619?
- Check whether you run 0x4m4 HexStrike AI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an OS command injection flaw in the Execute Endpoint of hexstrike_server.py, where the code/script parameter is not properly validated or sanitized before being used in system command execution. The attack vector is network-based, requiring no authentication or user interaction. An attacker can craft a malicious request containing shell metacharacters or command chaining syntax to execute arbitrary commands with the privileges of the server process. The vulnerability has been publicly disclosed and no patch has been confirmed from the project maintainers as of the advisory date.
Affected products
- 0x4m4 HexStrike AI up to d689933ff579d839c676c82b231f8e98326c5f04
Timeline
- 2026-09-14: disclosed: Vulnerability publicly disclosed
- 2026-09-14: advisory: CVE-2026-90619 published