Skip to main content
CVE-2026-114463VulnerabilityPublished Updated

Nous Research Hermes Agent · Webhook Platform Gateway

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-114463· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 21:06 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Nous ResearchHermes AgentAffected
  • <=2026.8.19
Fixed in–
GitHubnousresearch/hermes-agentpkg:github/nousresearch/hermes-agentOther threatsAffected
  • <=2026.8.19
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the webhook platform gateway and monitor for suspicious activity involving route names containing colons. Avoid using route names with colons if possible.

Description

A vulnerability in Nous Research Hermes Agent's webhook platform gateway allows a remote attacker to escalate privileges by manipulating the session chat_id. The chat_id is constructed as webhook:{route_name}:{delivery_id}, and the route name is parsed by splitting on colons. If the route name contains a colon, this parsing can cause the authorization to resolve to a higher-privileged route than intended, enabling unauthorized access to privileged toolsets.

References

Community reviews

Loading reviews…