# CVE-2026-49956: Hermes WebUI < 0.51.269 Profile Isolation Bypass via sessions search

> Authenticated users can bypass profile isolation to read session titles and transcripts from other profiles in Hermes WebUI.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 9 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-mgxw-v6rh-wcv6

## What is CVE-2026-49956?

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

### Official description

Hermes WebUI before version 0.51.269 contains a profile isolation bypass vulnerability that allows authenticated users to access data belonging to other profiles by querying the session search endpoint without active-profile filtering. Attackers can send requests to the sessions search handler to retrieve session titles and transcript message content from profiles other than their own active profile.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-49956 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49956 is a high-severity missing authorization vulnerability in nesquena hermes-webui, published on 9 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-49956 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-49956/ (Markdown: https://insights.sbomify.com/CVE-2026-49956/index.md)
```

## Sources

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

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