dbcve.org
CWE-348Weakness · CWE-348

CVE-2026-58122

CRITICAL · 9.1 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 7 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.307 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to circumvent local-origin IP restrictions on onboarding endpoints by supplying a spoofed X-Forwarded-For header with a loopback address. Attackers can exploit this bypass to perform server-side request forgery against internal services including cloud metadata endpoints, overwrite LLM provider configuration and API keys with attacker-controlled values, or initiate OAuth device-code flows to obtain persistent access tokens stored in auth.json.

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.307 contains an authentication bypass vulnerability in onboarding endpoints that rely on local-origin IP restrictions. Attackers can bypass these restrictions by supplying a spoofed X-Header (X-Forwarded-For) with a loopback address (127.0.0.1), tricking the application into believing the request originates from localhost. This allows unauthenticated attackers to perform SSRF against internal/cloud metadata services, overwrite LLM provider configurations with attacker-controlled API keys, and initiate OAuth device-code flows to obtain persistent access tokens stored in auth.json.

MitigationUpgrade Hermes WebUI to version 0.51.307 or later, which addresses the X-Forwarded-For header validation bypass. Additionally, implement strict header validation and consider disabling trust of X-Forwarded-For headers for sensitive endpoints at the proxy/load balancer level.

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
None

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

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 Hermes WebUI installation
    Locate Hermes WebUI in your environment - check running processes, installed applications, or container images that may contain this software
    Affected if Hermes WebUI is present and version is below 0.51.307
  2. Determine installed version
    Use the application's version command, check the About page, or inspect version metadata in the installation directory
    Affected if Installed version is earlier than 0.51.307
  3. Verify onboarding endpoint exposure
    Confirm whether onboarding or setup endpoints are accessible without authentication - check routing configuration and endpoint accessibility
    Affected if Onboarding endpoints are reachable without authentication
  4. Check X-Forwarded-For trust configuration
    Inspect application or proxy configuration to determine if X-Forwarded-For headers are trusted for IP-based access control decisions
    Affected if The application or reverse proxy trusts X-Forwarded-For headers for IP restriction decisions on sensitive endpoints
  5. Inspect for unauthorized configuration changes
    Review LLM provider configuration files and auth.json for unexpected modifications, new API keys, or unauthorized OAuth tokens
    Affected if LLM provider configs contain unknown API keys, or auth.json contains unexpected OAuth tokens

A user is affected if Hermes WebUI version is below 0.51.307 and the onboarding endpoints are accessible with X-Forwarded-For header spoofing allowed.

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.307 or later, which addresses the X-Forwarded-For header validation bypass. Additionally, implement strict header validation and consider disabling trust of X-Forwarded-For headers for sensitive endpoints at the proxy/load balancer level.

Recommended fix High confidence

0.51.307 or later

  1. 1. Identify the current installed version of Hermes WebUI by checking the application version or package manager
  2. 2. If running a version before 0.51.307, plan for immediate upgrade due to critical severity (CVSS 9.1)
  3. 3. Backup the current installation including configuration files and any auth.json
  4. 4. Upgrade Hermes WebUI to version 0.51.307 or later by following the project's upgrade instructions
  5. 5. After upgrade, verify that the X-Forwarded-For header is no longer trusted for IP-based authentication decisions by reviewing the patch changes at the vendor commit
  6. 6. Test that onboarding endpoints properly reject requests with spoofed X-Forwarded-For headers
  7. 7. Verify all LLM provider configurations remain intact and have not been tampered with
  8. 8. Review auth.json for any unauthorized access tokens and rotate if necessary

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58122 — 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-58122 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