CVE-2026-114463
Hermes Agent through version 2026.8.19 is affected only when a webhook route name contains a colon and its prefix matches another route. The fix is a release that includes PR #115285.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
The webhook platform gateway in Nous Research Hermes Agent versions builds the session chat_id as webhook:{route_name}:{delivery_id} and re-derives the authorizing route by splitting that string, so a route name containing a ":" resolves toolset authorization to a different, higher-privileged prefix route than the one authenticated, which allows a remote attacker with the target HMAC to gain that higher-privileged route's toolsets.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Nous Research Hermes Agent
through 2026.8.19
References 3
GitHub · NousResearch/hermes-agent
GitHub · pinarsadioglu/security-advisories
Questions about CVE-2026-114463
What does this mean?
A route can gain the toolsets of another route it is not authorized for, such as terminal and file access. That can enable command execution on the host as the user running Hermes Agent.Source: github.com
Am I affected, and how do I check?
Versions up to and including 2026.8.19 are in the affected range. The bug needs a webhook route whose name contains a colon and whose prefix matches another route, so check the webhook route names in the deployment configuration.Source: github.com
What should I do about it?
Upgrade to a release that includes PR #115285. The advisory does not name a specific fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
Rename any webhook routes so that no route name contains a colon.Source: github.com