NousResearch hermes-agent 2026.4.23 CLI web-dashboard Interface hermes_cli/web_server.py _discover_dashboard_plugins HERMES_ENABLE_PROJECT_PLUGINS comparison
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in NousResearch hermes-agent 2026.4.23. Affected by this vulnerability is the function _discover_dashboard_plugins of the file hermes_cli/web_server.py of the component CLI web-dashboard Interface. Executing a manipulation of the argument HERMES_ENABLE_PROJECT_PLUGINS can lead to comparison.
This vulnerability is tracked as CVE-2026-9369. The attack is restricted to local execution. Moreover, an exploit is present.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability has been found in NousResearch hermes-agent 2026.4.23 and classified as problematic. This vulnerability affects the function _discover_dashboard_plugins of the file hermes_cli/web_server.py of the component CLI web-dashboard Interface. The manipulation of the argument HERMES_ENABLE_PROJECT_PLUGINS with an unknown input leads to a comparison vulnerability. The CWE definition for the vulnerability is CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared for download at gist.github.com. This vulnerability was named CVE-2026-9369. The exploitation appears to be easy. The attack needs to be approached locally. Technical details and also a public exploit are known.
It is possible to download the exploit at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-31581). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: ComparisonCWE: CWE-697
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/23/2026 Advisory disclosed05/23/2026 VulDB entry created
05/25/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-9369 (🔒)
GCVE (CVE): GCVE-0-2026-9369
GCVE (VulDB): GCVE-100-365332
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/23/2026 12:38Updated: 05/25/2026 08:00
Changes: 05/23/2026 12:38 (58), 05/25/2026 08:00 (1)
Complete: 🔍
Submitter: Eric-i
Cache ID: 216::103
Submit
Accepted
- Submit #812230: NousResearch hermes-agent 2026.4.23 Incorrect Comparison (CWE-697) (by Eric-i)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.