CVE-2026-11461
Deferred Deferred - Pending Action
Authorization Bypass in Hermes-Agent via Resume Endpoint

Publication date: 2026-06-07

Last updated on: 2026-06-07

Assigner: VulDB

Description
A vulnerability has been found in NousResearch hermes-agent up to 0.12.0. This affects the function resolve_session_by_title of the file hermes_state.py of the component resume Endpoint. Such manipulation of the argument Title leads to authorization bypass. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-07
Last Modified
2026-06-07
Generated
2026-06-08
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nousresearch hermes-agent to 0.12.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the NousResearch hermes-agent software, specifically in the function resolve_session_by_title within the hermes_state.py file of the resume Endpoint component. The issue arises when the argument Title is manipulated, which leads to an authorization bypass. This means an attacker can potentially gain unauthorized access by exploiting this flaw.

The attack can be launched remotely, and the exploit has already been publicly disclosed. The vendor was informed early but did not respond.

Impact Analysis

This vulnerability can allow an attacker to bypass authorization controls remotely, potentially gaining access to restricted sessions or data that should be protected. This unauthorized access could lead to exposure of sensitive information or unauthorized actions within the affected system.

Compliance Impact

This vulnerability allows unauthorized access to user sessions, exposing sensitive data such as API keys, personally identifiable information (PII), and system information. Such unauthorized data exposure and access can lead to violations of data protection regulations like GDPR and HIPAA, which mandate strict controls over access to personal and sensitive information.

Because the vulnerability enables session hijacking without authentication, it undermines confidentiality and integrity requirements critical to compliance with these standards. Organizations using affected versions of Hermes Agent may face increased risk of non-compliance due to potential data breaches resulting from this flaw.

Detection Guidance

This vulnerability can be detected by checking for unauthorized access or session hijacking attempts involving the Hermes Agent's /resume command or the resolve_session_by_title function. Since the exploit involves guessing or enumerating session titles to gain unauthorized access, monitoring logs for unusual or repeated access attempts to session titles can help detect exploitation.

Specifically, you can look for calls to the resolve_session_by_title function or database queries that retrieve session data without user identity filtering.

While no exact commands are provided in the resources, a general approach would be to audit database queries related to session titles and monitor network traffic for suspicious requests targeting the /resume endpoint or similar API calls.

Mitigation Strategies

Immediate mitigation steps include restricting access to the Hermes Agent instance to trusted users only, as the vulnerability requires only the ability to guess or enumerate session titles.

Since no patched versions are currently available, consider implementing network-level controls such as firewall rules or VPNs to limit exposure.

Additionally, monitor and audit session creation and access logs to detect suspicious activity and consider rotating any sensitive data (e.g., API keys) that may have been exposed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11461. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart