Skip to main content
VulnerabilityPublished Updated

CVE-2026-49973: nesquena hermes-webui · Missing Authentication

Affects nesquena hermes-webuiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.2 Critical : upgrade to 0.51.358 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 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.358.

Affected software

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

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 network access to the device during initial setup to trusted networks only to prevent unauthorized POST requests to the settings API endpoint.

Description

Hermes WebUI before version 0.51.358 contains an improper access control vulnerability that allows unauthenticated remote attackers to hijack initial setup by submitting the _set_password parameter to the settings API endpoint without any network origin restriction. Attackers on any reachable network can send a POST request to the settings endpoint during the first-run setup window to persist an arbitrary password hash, obtain a valid session cookie, and lock out the legitimate operator from their own instance.

References

Community reviews

Loading reviews…