# CVE-2026-6829: nesquena hermes-webui Arbitrary Workspace Directory Access

> Authenticated attackers can manipulate workspace paths to read or modify files outside the intended directory boundary in hermes-webui.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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:** 21 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-rppv-5944-crmm

## What is CVE-2026-6829?

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

### Official description

nesquena hermes-webui contains a trust-boundary failure vulnerability that allows authenticated attackers to set or change a session workspace to an arbitrary existing directory on disk by manipulating workspace path parameters in endpoints such as /api/session/new, /api/session/update, /api/chat/start, and /api/workspaces/add. Attackers can repoint a session workspace to a directory outside the intended trusted root and then use ordinary file read and write APIs to access or modify files outside the intended workspace boundary within the permissions of the hermes-webui process.

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

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


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

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

## Is CVE-2026-6829 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6829 is a medium-severity path traversal vulnerability in nesquena hermes-webui, published on 21 Apr 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-6829 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-6829/ (Markdown: https://insights.sbomify.com/CVE-2026-6829/index.md)
```

## Sources

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

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