CVE-2026-11461
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn authorization bypass vulnerability exists in the resume endpoint of NousResearch hermes-agent (versions up to 0.12.0). The resolve_session_by_title function in hermes_state.py fails to properly validate authorization when processing the Title argument, allowing unauthorized access to session data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify hermes-agent installationSearch for NousResearch hermes-agent files in your environment. Look for directories named 'hermes-agent', 'hermes', or similar NousResearch artifacts. Check package managers or container images for hermes-related packages.Affected if hermes-agent from NousResearch is installed in the environment
-
Locate hermes_state.pyFind the hermes_state.py file in the hermes-agent installation directory. This file should contain the resolve_session_by_title function that is vulnerable.Affected if hermes_state.py exists and contains the resolve_session_by_title function
-
Inspect authorization logic in resolve_session_by_titleExamine the resolve_session_by_title function in hermes_state.py. Look for code that validates user permissions, session ownership, or authorization tokens before returning session data. Check if the Title parameter is validated against the requesting user's permissions.Affected if The function lacks or has weak authorization checks on the Title parameter, allowing unauthorized session access
-
Determine if resume endpoint is exposedIdentify if the resume endpoint that calls resolve_session_by_title is accessible to network users. Check route definitions, API endpoints, or web service configurations that expose the resume functionality.Affected if The resume endpoint is exposed to network access without proper authentication or authorization guards
-
Check for input validation on Title parameterReview code that processes the Title argument in session-related functions. Verify if the Title parameter undergoes sanitization or validation to prevent manipulation of session access controls.Affected if The Title parameter accepts arbitrary values without validation, allowing attackers to access sessions they do not own
Your environment is affected if hermes-agent from NousResearch is deployed and the resolve_session_by_title function in hermes_state.py lacks proper authorization validation on the Title parameter before returning session data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authorization checks in the resolve_session_by_title function to validate user permissions before returning session information. The fix should ensure session access is restricted to authorized users regardless of Title parameter manipulation.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11461 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data