# CVE-2026-58174: Hermes WebUI < 0.51.521 - Cross-Profile Authorization Bypass via Unset Session Profile on Import

> Attackers can bypass profile isolation to read files from other users' workspaces by exploiting a null profile assignment during session import.

- **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:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-8j74-6fjm-pjr7

## What is CVE-2026-58174?

CVE-2026-58174 is a medium-severity missing authorization vulnerability in nesquena hermes-webui, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hermes WebUI before 0.51.521 validates the workspace of an imported session under the active named profile but constructs the Session object without setting its profile in the /api/session/import handler, so the imported session is persisted with a null profile. Because a null profile is treated as the default profile by the profile authorization check, a user on the default profile can export the imported session transcript and use its session identifier to read files from the named profile's workspace, defeating the application's profile isolation.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-58174 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58174 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58174 is a medium-severity missing authorization vulnerability in nesquena hermes-webui, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58174 exists.

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-58174/ (Markdown: https://insights.sbomify.com/CVE-2026-58174/index.md)
```

## Sources

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

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