CVE-2026-11322: Hermes WebUI Path Traversal Vulnerability – Credential Exposure Risk

Technical summary

This path traversal vulnerability (CWE-59) exists in Hermes WebUI's file and directory listing APIs, which resolve symbolic links without validating that the resolved target remains within the configured workspace root boundary. An authenticated attacker can supply specially crafted symlinks to the workspace APIs and successfully traverse to parent directories and arbitrary filesystem locations accessible to the server process. The lack of canonicalization or bounds checking on symlink resolution allows disclosure of sensitive files outside the workspace namespace.

Business impact

If exploited, an attacker with legitimate workspace access could exfiltrate high-value secrets stored on the same server, including SSH private keys for infrastructure access, cloud provider credentials, and application tokens. This creates a lateral movement pathway and credential compromise risk that directly undermines identity and access control boundaries. Organizations relying on Hermes WebUI for file management should assume that workspace isolation is not trustworthy in affected versions.

Affected systems

Hermes WebUI prior to version 0.51.221 is vulnerable. The vendor has not provided an exhaustive product list in public disclosures; verify your Hermes WebUI deployment version and cross-reference against vendor advisories to confirm exposure.

Exploitability

Exploitation requires an authenticated user account with workspace access—this is not an unauthenticated vulnerability. However, the attack surface is relatively broad: any user able to create or modify files within a workspace can craft symlinks, and the barrier to weaponization is low. Once crafted, symlink-based attacks are straightforward to execute and reliably expose sensitive data. Network accessibility is required, but no unusual conditions or user interaction are necessary. The CVSS 3.1 score of 6.5 (Medium) reflects the authentication requirement, high confidentiality impact, and network-based delivery.

Remediation

Upgrade Hermes WebUI to version 0.51.221 or later. This version enforces proper path validation to ensure symlink targets remain within workspace boundaries. If immediate patching is not feasible, restrict workspace access to trusted users only and monitor for suspicious file access patterns within workspaces.

Patch guidance

Apply Hermes WebUI version 0.51.221 or a later stable release. Verify the applied version via the WebUI version endpoint or administrative console. Test the upgrade in a non-production environment first to ensure compatibility with your workspace configurations. Refer to the vendor's release notes for any breaking changes or migration guidance.

Detection guidance

Monitor Hermes WebUI access logs for repeated or systematic requests to workspace file listing and retrieval APIs, especially patterns involving symlink creation or access to files with path components like '..' or absolute paths. Watch for API calls that succeed in returning file contents from unexpected filesystem locations. File integrity monitoring on sensitive system files (SSH keys, credential stores, cloud config files) can alert to unauthorized read access. Network-based detection of symlink payloads in API requests may be possible if your monitoring tools can inspect request bodies.

Why prioritize this

This vulnerability merits prompt patching because it directly threatens credential confidentiality for any organization storing secrets accessible to the Hermes WebUI process. The requirement for authentication reduces urgency compared to unauthenticated path traversal, but the high-value nature of typical targets (SSH keys, cloud credentials) and the low exploitation complexity make it a priority ahead of vulnerabilities with lower confidentiality impact. Organizations handling sensitive deployments should patch within 30 days.

Risk score, explained

The CVSS 3.1 score of 6.5 (Medium) balances the high confidentiality impact (H) against the authentication requirement (PR:L). The vulnerability does not affect integrity or availability, limiting the severity ceiling. However, the authenticated-user requirement should not be underestimated: insider threats, compromised accounts, or overly permissive workspace sharing can quickly turn this into an active attack vector. The practical risk is often higher than the CVSS score suggests in environments with relaxed user access controls.

Frequently asked questions