Skip to main content
VulnerabilityPublished Updated

CVE-2026-6830: nesquena hermes-webui · Resource Exposure

Affects nesquena hermes-webuiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to PR #351 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in PR #351
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade nesquena hermes-webui to PR #351.

Affected software

ProductAffectedFixed in
nesquenahermes-webuiAffected
  • =0
Fixed in
  • PR #351
GitHubnesquena/hermes-webuipkg:github/nesquena/hermes-webuiOther threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should avoid switching profiles in a way that relies on environment variable isolation or manually clear environment variables between profile switches if possible.

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.

References

Community reviews

Loading reviews…