Skip to main content
VulnerabilityPublished Updated

CVE-2026-55198: nesquena hermes-webui · Insecure Direct Object Reference

Affects nesquena hermes-webuiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.51.443 soon.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.51.443
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 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

Upgrade nesquena hermes-webui to 0.51.443.

Affected software

ProductAffectedFixed in
nesquenahermes-webuiAffected
  • <0.51.443
Fixed in
  • 0.51.443
GitHubhermes-webuipkg:github/hermes-webuiOther threatsAffected
  • <0.51.443
Fixed in
  • 0.51.443

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

AI-suggested

If you cannot patch yet, restrict access to the session export endpoint to trusted users only and consider implementing additional access controls or monitoring for suspicious access patterns related to session exports.

Description

Hermes WebUI before 0.51.443 contains an authorization bypass vulnerability in the session export endpoint that allows authenticated users to access sessions from other profiles. The _handle_session_export handler in api/routes.py fails to verify active-profile ownership before serializing session data, enabling attackers to exfiltrate foreign session transcripts by guessing or knowing session identifiers.

References

Community reviews

Loading reviews…