CVE-2026-22798

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

hermes is an implementation of the HERMES workflow to automatize software publication with rich metadata. From 0.8.1 to before 0.9.1, hermes subcommands take arbitrary options under the -O argument. These have been logged in raw form. If users provide sensitive data such as API tokens (e.g., via hermes deposit -O invenio_rdm.auth_token SECRET), these are written to the log file in plain text, making them available to whoever can access the log file. This vulnerability is fixed in 0.9.1.

CVSS v3
5.0
EG Score
5.0(medium)
EG Risk
23(Track)
EG Risk 23/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

January 12, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 9, 2026
Patch available. Sources: github, github_commit.
github Patch Available

Raw options logging may disclose secrets passed in via subcommand options argument · Advisory · softwarepub/hermes · GitHub

https://github.com/softwarepub/hermes/security/advisories/GHSA-jm5j-jfrm-hm23
github_commit Patch Available

commit 90cb86acd026 (softwarepub/hermes)

Patch available: softwarepub/hermes v0.9.1 (contains commit 90cb86acd026)

https://github.com/softwarepub/hermes/commit/90cb86acd026e7841f2539ae7a1b284a7f263514
github_commit Patch Available

commit 7f64f102e916 (softwarepub/hermes)

Patch available: softwarepub/hermes v0.8.1 (contains commit 7f64f102e916)

https://github.com/softwarepub/hermes/commit/7f64f102e916c76dc44404b77ab2a80f5a4e59b1

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
hermes0.8.1, 0.9.00.9.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-09-19 05:00 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 08:25 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 14:52 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-09 20:30 UTCEG score recompute
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-08 01:00 UTCEG score recompute
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-06 05:59 UTCEG score recompute▼ 0.90
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-04 15:10 UTCEPSS rescore
  19. 2026-08-04 10:38 UTCEPSS rescore
  20. 2026-08-03 10:35 UTCEPSS rescore
  21. 2026-08-02 02:26 UTCEPSS rescore
  22. 2026-08-01 04:15 UTCEPSS rescore
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-27 14:13 UTCEPSS rescore
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-25 14:17 UTCEPSS rescore
  28. 2026-07-25 14:17 UTCEPSS rescore
  29. 2026-07-24 14:17 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 10:49 UTCOSV refresh
  33. 2026-07-23 03:06 UTCEG score recompute
  34. 2026-07-22 14:08 UTCEPSS rescore
  35. 2026-07-21 15:24 UTCEPSS rescore
  36. 2026-07-21 15:24 UTCEPSS rescore
  37. 2026-07-20 17:08 UTCEPSS rescore
  38. 2026-07-19 14:31 UTCEPSS rescore
  39. 2026-07-19 14:31 UTCEPSS rescore
  40. 2026-07-19 02:29 UTCEPSS rescore
  41. 2026-07-19 02:28 UTCEPSS rescore
  42. 2026-07-16 17:03 UTCEPSS rescore
  43. 2026-07-16 17:03 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-15 02:00 UTCEPSS rescore
  48. 2026-07-13 22:30 UTCEPSS rescore
  49. 2026-07-13 06:13 UTCEPSS rescore
  50. 2026-07-13 06:13 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-12 05:46 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-08 15:15 UTCEPSS rescore
  56. 2026-07-08 15:15 UTCEPSS rescore
  57. 2026-07-07 13:46 UTCEPSS rescore
  58. 2026-07-06 16:27 UTCEPSS rescore
  59. 2026-07-06 16:27 UTCEPSS rescore
  60. 2026-07-06 06:02 UTCOSV refresh
  61. 2026-07-06 02:23 UTCEPSS rescore
  62. 2026-07-06 02:23 UTCEPSS rescore
  63. 2026-07-05 02:30 UTCEPSS rescore
  64. 2026-07-04 06:31 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-07-01 15:06 UTCEPSS rescore
  68. 2026-06-30 23:22 UTCEPSS rescore
  69. 2026-06-30 23:22 UTCEPSS rescore
  70. 2026-06-29 14:06 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 14:07 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-28 04:56 UTCEPSS rescore
  75. 2026-06-27 03:08 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22798?
CVE-2026-22798 is a medium vulnerability published on January 12, 2026. hermes is an implementation of the HERMES workflow to automatize software publication with rich metadata. From 0.8.1 to before 0.9.1, hermes subcommands take arbitrary options under the -O argument. These have been logged in raw form. If users provide sensitive data such as API tokens (e.g., via…
When was CVE-2026-22798 disclosed?
CVE-2026-22798 was first published in the National Vulnerability Database on January 12, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22798 actively exploited?
CVE-2026-22798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.8% of all scored CVEs.
What is the CVSS score of CVE-2026-22798?
CVE-2026-22798 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-22798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22798, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-22798

Explore →

Is Your Infrastructure Affected by CVE-2026-22798?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs