Quick answers
- Is CVE-2026-9350 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-9350 being exploited in the wild.
- How severe is CVE-2026-9350?
- High severity, with a CVSS score of 7.3, published 24 May 2026.
- Which products and versions are affected?
- NousResearch hermes-agent up to 2026.4.16.
- Is there a fix for CVE-2026-9350?
- 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-9350 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-9350?
- Check whether you run NousResearch Hermes Agent. 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
A missing authorization vulnerability exists in the `check_all_command_guards` function within `tools/approval.py`. The root cause is an insecure default fallback: when the agent is run via `batch_runner.py`, it fails to set interactive environment variables (such as `HERMES_INTERACTIVE`), causing the safety logic to treat the execution context as safe and auto-approve all commands. An attacker can exploit this by embedding prompt injection payloads in JSONL datasets processed by the Batch Runner. This bypasses regex pattern matching and security scanning, leading to remote code execution (RCE) on the host machine. As of the advisory date, the vendor has not responded to the disclosure.
Affected products
- NousResearch hermes-agent up to 2026.4.16
Timeline
- 2026-04-24: disclosed: Initial discovery and PoC published on GitHub Gist
- 2026-05-24: advisory: CVE-2026-9350 published via VulDB/NVD