Quick answers
- Is CVE-2026-9369 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-9369 being exploited in the wild.
- How severe is CVE-2026-9369?
- Medium severity, with a CVSS score of 5.3, published 24 May 2026.
- Which products and versions are affected?
- NousResearch Hermes Agent 2026.4.23; hermes-agent (PyPI) ECOSYSTEM:introduced=0,fixed=0.15.0.
- Is there a fix for CVE-2026-9369?
- Yes. hermes-agent (PyPI): upgrade to 0.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-9369 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-9369?
- Check whether you run NousResearch Hermes Agent or hermes-agent (PyPI) 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.
How to fix
- hermes-agent (PyPI): upgrade to 0.15.0 or later
pip install "hermes-agent>=0.15.0"
Technical details
A vulnerability exists in the `_discover_dashboard_plugins` function within `hermes_cli/web_server.py` due to an incorrect comparison of the `HERMES_ENABLE_PROJECT_PLUGINS` environment variable. The application uses `os.environ.get()` instead of a boolean-aware utility, causing non-empty strings like "false" or "0" to be evaluated as truthy. An attacker can exploit this by placing a malicious `manifest.json` and Python payload within a repository's `.hermes/plugins/` directory. When a user starts the web dashboard (`hermes --web`) while inside the malicious repository, the agent automatically imports and executes the attacker's code. This bypasses intended security opt-out configurations and leads to local code execution. The issue is addressed in version 0.15.0.
Affected products
- NousResearch hermes-agent < 0.15.0
Identifiers
- CVE-2026-9369
- GHSA-cv5c-mh6j-wvp9
- PYSEC-2026-2512
Timeline
- 2026-04-24: disclosed: Initial discovery and PoC report created
- 2026-05-24: advisory: NVD publication of CVE-2026-9369
- 2026-05-26: advisory: GitHub Advisory published
- 2026-06-30: patched: GitHub Advisory updated with patch information