CVE-2026-84287 Overview
A denial of service vulnerability affects NousResearch hermes-agent version 0.18.0. The flaw resides in unspecified functionality within gateway/platforms/api_server.py, part of the Session Chat Interface component. Remote attackers with low-level authenticated access can trigger the condition without user interaction, causing service unavailability. The exploit has been publicly disclosed and may already be in use by threat actors. According to the disclosure, the vendor was contacted before public release but did not respond. The weakness is categorized under [CWE-404: Improper Resource Shutdown or Release].
Critical Impact
Remote authenticated attackers can disrupt the availability of the hermes-agent Session Chat Interface, degrading agentic AI workflows that depend on the API gateway.
Affected Products
- NousResearch hermes-agent 0.18.0
- Component: Session Chat Interface (gateway/platforms/api_server.py)
- Deployments exposing the hermes-agent API server to network access
Discovery Timeline
- 2026-09-01 - CVE-2026-84287 published to NVD
- 2026-09-02 - Last updated in NVD database
- 2026-09-03 - EPSS score assessment recorded
Technical Details for CVE-2026-84287
Vulnerability Analysis
The vulnerability sits inside the api_server.py module that powers the Session Chat Interface of hermes-agent. Improper resource release [CWE-404] allows a remote attacker to submit crafted requests that the server fails to reclaim, exhausting available capacity. Once resources are depleted, legitimate chat sessions cannot be established or processed. The attack requires authentication at a low privilege level and does not need user interaction. Because hermes-agent commonly acts as an orchestration gateway for AI agents, downstream automation, model inference calls, and dependent tooling stall when the interface fails.
Root Cause
The root cause is improper resource shutdown or release in the session handling path of the API server. The affected code does not correctly free session state, connections, or backing resources allocated during chat interactions. Repeated invocation forces the process into a resource-starved state until it can no longer service new requests.
Attack Vector
Exploitation occurs over the network against an exposed hermes-agent API endpoint. The attacker must hold valid low-privilege credentials to reach the Session Chat Interface. From there, repeated malformed or resource-intensive session interactions drive the server into denial of service. Public proof-of-concept material is available in the referenced GitHub DoS Report and the VulDB entry for CVE-2026-84287.
No verified exploit code is included here. Refer to the linked advisories for technical reproduction details.
Detection Methods for CVE-2026-84287
Indicators of Compromise
- Sudden spike in session initialization requests to gateway/platforms/api_server.py endpoints from a single authenticated principal
- Unclosed or long-lived chat sessions accumulating beyond normal operational baselines
- API server process consuming abnormal memory, file descriptors, or thread counts before becoming unresponsive
- Elevated 5xx responses or connection timeouts reported by clients of the Session Chat Interface
Detection Strategies
- Instrument the hermes-agent API server with metrics for active sessions, open sockets, and heap usage, and alert on rate-of-change anomalies
- Correlate authenticated user identifiers with request volume to identify low-privilege accounts generating disproportionate session traffic
- Deploy request-rate profiling at the reverse proxy or ingress layer in front of hermes-agent
Monitoring Recommendations
- Forward API server logs and resource telemetry to a centralized analytics pipeline for anomaly review
- Track process restarts and out-of-memory events on hosts running hermes-agent
- Monitor authentication logs for credentials with unusual session-creation patterns
How to Mitigate CVE-2026-84287
Immediate Actions Required
- Restrict network exposure of the hermes-agent Session Chat Interface to trusted management networks or VPN segments
- Rotate and audit credentials for accounts with access to the API server, and remove unused low-privilege accounts
- Apply rate limits and per-user session quotas at an upstream proxy until an official patch is available
- Track the VulDB advisory for CVE-2026-84287 for vendor fix status
Patch Information
At the time of publication, no vendor patch has been released. The disclosure notes that NousResearch was contacted about the issue but did not respond. Operators should monitor the project repository and the referenced VulDB vulnerability entry for future updates and pin deployments away from hermes-agent 0.18.0 where feasible.
Workarounds
- Place hermes-agent behind an authenticating reverse proxy that enforces request throttling and concurrent-session limits per principal
- Configure process supervisors to cap memory and file-descriptor usage, and to automatically restart the API server on resource exhaustion
- Disable the Session Chat Interface for tenants that do not require it, reducing the reachable attack surface
- Segment hermes-agent workloads so that a single service outage does not cascade into dependent agentic AI pipelines
Refer to the GitHub DoS Report for reproduction context when validating mitigations in a controlled environment.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
