Live › vulnerability › CVE-2026-114463
Go to dashboardHermes Agent's webhook gateway builds session IDs from the route name and delivery ID, then re-derives the authorizing route by splitting that string on colons. A route name containing a colon can be matched to a different, higher-privileged route, so a remote attacker holding the target's HMAC secret can gain that route's toolsets.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Deployments of Hermes Agent that expose the webhook platform gateway and define several webhook routes with differing privileges, where an attacker holds a route's HMAC secret. Installations that do not enable the webhook gateway, or that use only one route, are less exposed. The sources do not say which versions are fixed.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-114463")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.