Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-58122 – Authentication Bypass – Hermes WebUI before 0.51.307

Be the first to know when new zero-days emerge:

Summary

CVE-2026-58122 is a critical authentication bypass vulnerability in Hermes WebUI (nesquena/hermes-webui), an AI agent web interface commonly deployed internet-facing. By supplying a spoofed loopback address in the X-Forwarded-For HTTP header, unauthenticated remote attackers can circumvent local-origin IP restrictions enforced on onboarding endpoints, enabling server-side request forgery, LLM configuration hijacking, and persistent OAuth token theft. All versions prior to 0.51.307 are affected, and the vulnerability carries a CVSS 4.0 score of 9.3 (Critical).

Technical details

  • Root cause: The application improperly trusts the client-supplied X-Forwarded-For HTTP header when evaluating IP-based access controls on sensitive onboarding endpoints. By setting this header to a loopback address (e.g., 127.0.0.1 or ::1), an unauthenticated remote attacker can impersonate a local-origin request and gain access to restricted onboarding functionality (CWE-348: Use of Less Trusted Source).
  • Trigger conditions: The affected onboarding endpoints are reachable over the network on a standard Hermes WebUI deployment. No authentication, prior user interaction, or elevated privileges are required — a single crafted HTTP request is sufficient.
  • Attack vector: Network-accessible; exploitation requires only the addition of a spoofed X-Forwarded-For header to an HTTP request targeting the onboarding API.
  • Impact:
    • Server-Side Request Forgery (SSRF): The bypass enables SSRF against internal services, including cloud metadata endpoints (e.g., AWS IMDSv1, GCP instance metadata), allowing attackers to harvest cloud credentials from the deployment environment.
    • LLM configuration hijack: Attackers can overwrite LLM provider configuration and API keys with attacker-controlled values, achieving persistent interception or manipulation of all AI interactions processed by the instance.
    • Persistent OAuth access: Attackers can initiate OAuth device-code flows to obtain persistent access tokens, which are stored in auth.json and provide long-term unauthorized access to the deployment.

Affected software

  • Hermes WebUI (nesquena/hermes-webui) — all versions prior to 0.51.307

Severity

CVSS 4.0 base score 9.3 (Critical)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to Hermes WebUI v0.51.307 or later. This release (commit 70596e6, PR #3764, published June 7, 2026) patches the onboarding endpoint spoofing vulnerability.
  • If immediate patching is not feasible: Restrict network-level access to the onboarding API endpoints via firewall rules or reverse-proxy configuration, permitting requests only from verified trusted internal IP ranges. Do not rely solely on application-layer IP checks as a security control.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge