Is there a public PoC exploit available for EUVD-2026-34992?

Yes, a public proof-of-concept exploit is available for EUVD-2026-34992. Prioritise patching immediately. EPSS: 0.0%.

hermes-agent EUVD-2026-34992

Q: What is the CVSS score of EUVD-2026-34992?

EUVD-2026-34992 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

| CVE-2026-11461 LOW

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-06-07 VulDB

GHSA-9396-xwf6-94hp

Authentication Bypass Hermes Agent

2.1

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Jun 07, 2026 - 22:22 NVD

MEDIUM LOW

CVSS changed

Jun 07, 2026 - 22:22 NVD

6.3 (MEDIUM) 2.1 (LOW)

Analysis Generated

Jun 07, 2026 - 22:13 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Authorization bypass in NousResearch hermes-agent up to 0.12.0 allows remote low-privileged authenticated attackers to access or manipulate sessions belonging to other users by supplying an arbitrary session title to the resume endpoint's resolve_session_by_title function without ownership verification. A public proof-of-concept exploit has been disclosed via GitHub Gist, and the vendor did not respond to pre-disclosure contact, meaning no patch is currently available. With CVSS 6.3 and a temporal exploit-partial modifier, this presents elevated practical risk in multi-tenant or shared-instance deployments where session isolation is a security boundary.

Technical ContextAI

The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): the application uses a user-supplied title argument as a direct lookup key to retrieve session objects via resolve_session_by_title in hermes_state.py, without verifying that the authenticated requester owns or is authorized to access the matched session. hermes-agent is an AI agent orchestration framework by NousResearch; the resume endpoint is responsible for restoring prior agent sessions by name. Because session titles are not scoped to the requesting user's identity before object retrieval, any authenticated user can enumerate or target sessions by title. The affected CPE is cpe:2.3:a:nousresearch:hermes-agent:*:*:*:*:*:*:*:* covering all versions through 0.12.0.

RemediationAI

No vendor-released patch has been identified at time of analysis - the vendor did not respond to pre-disclosure contact, so no fix version is confirmed. As an immediate hotfix, operators should add server-side ownership validation directly in resolve_session_by_title within hermes_state.py to cross-check that the session retrieved by title belongs to the currently authenticated requesting user before returning it; this code-level change can be applied without waiting for an upstream release. As a compensating network control, restrict access to the resume endpoint via reverse proxy authentication middleware or firewall rules to ensure only trusted, known users can reach it, with the trade-off of reducing legitimate accessibility. Monitor the VulDB entry at https://vuldb.com/vuln/369081 and the NousResearch upstream repository for any patch releases. Review the public PoC at https://gist.github.com/YLChen-007/c2d162e9c8d39584223683cdcba98607 to understand the exact exploitation pattern and validate any applied fix.