CVE-2026-22798: softwarepub hermes · Sensitive Data in Logs
Affects softwarepub hermesSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.9.1 when convenient.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.9.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade hermes and softwarepub/hermes to 0.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| softwarepubhermes | Affected
| Fixed in
|
GitHubsoftwarepub/hermespkg:github/softwarepub/hermesOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary mitigation is to upgrade hermes to version 0.9.1 or later, where the vulnerability is fixed. Until upgrade is possible, organizations should: 1) Avoid passing sensitive information such as API tokens via the -O argument or any command-line options that may be logged. Use environment variables or secure credential stores instead. 2) Restrict access to hermes log files to only trusted administrators and processes, enforcing strict file permissions and monitoring access logs. 3) Implement log management policies that include regular log rotation and secure archival to minimize exposure time. 4) Educate users and administrators about the risks of including sensitive data in command-line arguments and logs. 5) Monitor for unusual access patterns or token usage that could indicate compromise. 6) Consider isolating hermes execution environments to reduce the risk of local privilege escalation or unauthorized log access. 7) Review and audit existing logs for exposed tokens and rotate or revoke any compromised credentials immediately. These steps go beyond generic advice by focusing on operational practices specific to this vulnerability's nature.
Description
CVE-2026-22798 is a medium severity vulnerability in the softwarepub hermes tool versions 0.8.1 up to but not including 0.9.1. The issue arises because hermes logs arbitrary options passed via the -O argument in raw form, including sensitive data such as API tokens. This results in sensitive information being stored in plaintext within log files, exposing it to any user or process with access to those logs. Exploitation requires local access with limited privileges and some user interaction, but can lead to a compromise of integrity through token theft. The vulnerability has been fixed in version 0.9.