# CVE-2026-6830: Nesquena Hermes WebUI Environment Variable Credential Leakage via Profile Switch

> Attackers can access sensitive API keys from one profile in another due to environment variables not being cleared during profile switching.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-vvfr-g83f-8qcv

## What is CVE-2026-6830?

CVE-2026-6830 is a medium-severity vulnerability in nesquena hermes-webui, published on 21 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

nesquena hermes-webui contains an environment variable leakage vulnerability where profile switching does not clear environment variables from the previously active profile before loading the next profile. Attackers or users can exploit additive dotenv reload behavior to access provider API keys and other sensitive secrets from one profile context in another profile, breaking expected security isolation between profiles.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2026-6830 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6830 is a medium-severity vulnerability in nesquena hermes-webui, published on 21 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6830 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-6830/ (Markdown: https://insights.sbomify.com/CVE-2026-6830/index.md)
```

## Sources

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

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