dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-58123

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Hermes WebUI before 0.51.788 contains an unauthenticated remote code execution vulnerability that allows remote attackers to execute arbitrary shell commands by accessing the embedded terminal API endpoints without credentials. Attackers can create a session, attach a PTY shell, and write arbitrary commands through the terminal input endpoint to achieve full command execution as the server process user via four sequential unauthenticated HTTP requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Hermes WebUI before 0.51.788 contains an unauthenticated remote code execution vulnerability in its embedded terminal API. Attackers can execute arbitrary shell commands by making four sequential unauthenticated HTTP requests to create a session, attach a PTY shell, and write commands through the terminal input endpoint, achieving full command execution as the server process user.

MitigationUpgrade Hermes WebUI to version 0.51.788 or later to patch the vulnerability. If immediate upgrade is not possible, restrict network access to the WebUI interface to trusted IPs only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Hermes WebUI is running in your environment
    Review your web application inventory, running services, or container images to confirm Hermes WebUI is deployed. Check process lists, Docker containers, or service manifests for 'hermes' or 'webui' components.
    Affected if Hermes WebUI is present and accessible on the network
  2. Determine the installed Hermes WebUI version
    Access the WebUI admin panel, check the application's about page, examine HTTP response headers from the server, or review deployment configuration files and Docker image tags for the version number.
    Affected if The version is earlier than 0.51.788 or the version cannot be determined (assume affected)
  3. Verify if the terminal API endpoint accepts unauthenticated requests
    Send an HTTP request to the terminal API endpoints mentioned in the documentation (typically /api/terminal/session or similar paths) without providing authentication credentials and observe the response.
    Affected if The API returns a valid session or accepts commands without requiring authentication tokens or login
  4. Confirm network exposure of the WebUI interface
    Review firewall rules, reverse proxy configuration, or cloud security groups to determine if the Hermes WebUI HTTP port is exposed to untrusted networks or the public internet.
    Affected if The interface is reachable from untrusted IP addresses or the internet without network-level access controls

You are affected if Hermes WebUI version is below 0.51.788 and the terminal API is accessible without authentication from an untrusted network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Hermes WebUI to version 0.51.788 or later to patch the vulnerability. If immediate upgrade is not possible, restrict network access to the WebUI interface to trusted IPs only.

Recommended fix High confidence

Upgrade to Hermes WebUI version 0.51.788 or later

  1. 1. Identify the current Hermes WebUI version running in your environment
  2. 2. If running a version before 0.51.788, plan for upgrade to version 0.51.788 or later
  3. 3. Download or pull the updated Hermes WebUI version 0.51.788 or latest stable release
  4. 4. Back up any existing configuration and data files
  5. 5. Stop the current Hermes WebUI service
  6. 6. Install or deploy the upgraded version (0.51.788 or newer)
  7. 7. Restart the Hermes WebUI service
  8. 8. Verify the service is running correctly and the terminal API now requires authentication
Caveat Review release notes for any breaking changes between your current version and 0.51.788 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58123 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58123 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data