# CVE-2026-22677: Hermes WebUI < 0.51.44 Path Traversal via Session Import Endpoint

> Authenticated attackers can read arbitrary files via path traversal in the session import endpoint of Hermes WebUI.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-wvw9-5wfm-7729

## What is CVE-2026-22677?

CVE-2026-22677 is a medium-severity path traversal vulnerability in nesquena hermes-webui, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hermes WebUI prior to 0.51.44 contains a path traversal vulnerability in the session import endpoint that allows authenticated attackers to read arbitrary files by importing a crafted session with an unrestricted workspace value. Attackers can supply a blocked filesystem root in the workspace field and subsequently use relative paths in the session file API to access any file readable by the WebUI process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-22677?


## How do I fix CVE-2026-22677?

No fix has been published for CVE-2026-22677 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22677 being exploited?

There is no known exploitation of CVE-2026-22677 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22677 and fix it if it is affected.

What it is: CVE-2026-22677 is a medium-severity path traversal vulnerability in nesquena hermes-webui, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22677 in the wild and no public exploit code.

Affected product: nesquena hermes-webui. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22677/ (Markdown: https://insights.sbomify.com/CVE-2026-22677/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22677
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22677
- OSV: https://osv.dev/vulnerability/CVE-2026-22677

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22677/
Summaries are generated and may contain mistakes; the official description above is the record.