Security readout for executives and security teams
Plain-English summary
Hermes logged raw subcommand options, which could include secrets such as repository API tokens. Anyone with access to the log file could read those values in plain text. This affects hermes versions 0.8.1 through before 0.9.1 and is fixed in 0.9.1.
Executive priority
Treat as a targeted cleanup and credential-rotation issue, not an internet-wide emergency. Prioritize teams using hermes for publication workflows, especially where logs are centralized or broadly accessible.
Technical view
CVE-2026-22798 is a CWE-532 sensitive information exposure in softwarepub hermes. Arbitrary values supplied through the -O subcommand option were written to logs without redaction. The advisory cites examples such as invenio_rdm.auth_token. CVSS is 5.9 with local access, low complexity, low privileges, and user interaction required.
Likely exposure
Exposure is most likely where hermes was used with -O options containing tokens or other secrets, and where local users, CI systems, support staff, or log aggregation tools can access hermes log files.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked KEV. Abuse depends on access to affected log files after a user supplied sensitive data through hermes options.
Researcher notes
The primary evidence is the GitHub advisory and related commits. The source description states fixed in 0.9.1. The CVSS vector indicates local access and user interaction. Provided sources do not establish remote exploitation or public weaponization.
Mitigation direction
- Upgrade hermes to version 0.9.1 or later.
- Review vendor advisory and commits for the exact logging change.
- Rotate any secrets that may have been passed through -O options.
- Restrict access to historical hermes logs until reviewed.
- Remove exposed secrets from retained logs where operationally safe.
Validation and detection
- Inventory hermes installations and identify versions 0.8.1 through before 0.9.1.
- Check whether workflows used -O options for authentication tokens or secrets.
- Review accessible hermes logs for accidental plaintext secret entries.
- Confirm upgraded systems no longer log raw sensitive option values.
- Verify rotated credentials replace any suspected exposed tokens.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-532: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22798 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N1.54Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/softwarepub/hermes/security/advisories/GHSA-jm5j-jfrm-hm23CVE reference · x_refsource_CONFIRM
- https://github.com/softwarepub/hermes/commit/7f64f102e916c76dc44404b77ab2a80f5a4e59b1CVE reference · x_refsource_MISC
- https://github.com/softwarepub/hermes/commit/90cb86acd026e7841f2539ae7a1b284a7f263514CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information into Log File
Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.