CVE-2026-82020

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. A secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Hermes Agent 0.16.0 prior to 0.17.0 contains an improper path restriction vulnerability that allows attackers who can influence ingested message content to overwrite the credential store by bypassing sensitive-path guards that excluded the auth.json file. Attackers can craft malicious messages directing the agent's file-write tooling to overwrite the credential store without triggering any path-based protection, enabling credential tampering or unauthorized access.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

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 (value × EchelonGraph’s weight)
Severity68% × 45%
The EG Score, 6.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Aug 28, 2026
Patch available. Sources: github_release, github_pr, github_commit.
Web page

Hermes Agent 0.16.0 < 0.17.0 Credential Store Overwrite via File-Write Tool | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hermes-agent-credential-store-overwrite-via-file-write-tool
GitHub commit

commit 2b67e96aec2a (NousResearch/hermes-agent)

Fix landed in NousResearch/hermes-agent commit 2b67e96aec2a — awaiting tagged release

https://github.com/NousResearch/hermes-agent/commit/2b67e96aec2aa2abd5e94b544cda8e564c75f9f5
GitHub commit

commit da28d5d11395 (NousResearch/hermes-agent)

Fix landed in NousResearch/hermes-agent commit da28d5d11395 — awaiting tagged release

https://github.com/NousResearch/hermes-agent/commit/da28d5d113956dcf803d5cff552a120740a96a59
GitHub pull request

fix(approval): gate sensitive user-file terminal writes

Fix merged in NousResearch/hermes-agent PR #45821 on 2026-06-13 — awaiting tagged release

https://github.com/NousResearch/hermes-agent/pull/45821
GitHub release Patch Available

Hermes Agent v0.17.0 (v2026.6.19)

Patch available: NousResearch/hermes-agent v2026.6.19

https://github.com/NousResearch/hermes-agent/releases/tag/v2026.6.19

Vendor Advisories for CVE-2026-82020(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 76× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-12 14:56 UTCEG score recompute
  4. 2026-10-11 19:20 UTCEG score recompute
  5. 2026-10-11 16:36 UTCEG score recompute
  6. 2026-10-11 13:54 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-10 05:16 UTCEG score recompute
  10. 2026-10-10 05:16 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-09 02:37 UTCEG score recompute
  13. 2026-10-09 02:37 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-07 09:50 UTCEG score recompute
  17. 2026-10-07 09:50 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-06 07:27 UTCEG score recompute
  20. 2026-10-06 07:27 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-05 04:34 UTCEG score recompute
  23. 2026-10-05 04:34 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-10-04 02:33 UTCEG score recompute
Show 73 more
  1. 2026-10-04 02:33 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-03 00:32 UTCEG score recompute
  4. 2026-10-03 00:32 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  5. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-10-01 22:31 UTCEG score recompute
  7. 2026-10-01 22:31 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-09-30 19:48 UTCEG score recompute
  10. 2026-09-30 19:48 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  11. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-09-29 14:11 UTCEG score recompute
  13. 2026-09-29 14:11 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  14. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-09-28 12:05 UTCEG score recompute
  16. 2026-09-28 12:05 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  17. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-09-27 10:04 UTCEG score recompute
  19. 2026-09-27 10:04 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-26 08:03 UTCEG score recompute
  22. 2026-09-26 08:03 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  23. 2026-09-25 04:29 UTCEG score recompute
  24. 2026-09-25 04:29 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-24 02:28 UTCEG score recompute
  27. 2026-09-24 02:28 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  28. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  29. 2026-09-23 00:26 UTCEG score recompute
  30. 2026-09-23 00:26 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  31. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  32. 2026-09-21 22:24 UTCEG score recompute
  33. 2026-09-21 22:23 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  34. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  35. 2026-09-20 20:21 UTCEG score recompute
  36. 2026-09-20 20:21 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  37. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  38. 2026-09-19 18:20 UTCEG score recompute
  39. 2026-09-19 18:20 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  40. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  41. 2026-09-18 16:19 UTCEG score recompute
  42. 2026-09-18 16:19 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  43. 2026-09-17 13:59 UTCEG score recompute
  44. 2026-09-17 13:59 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  45. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  46. 2026-09-16 11:58 UTCEG score recompute
  47. 2026-09-16 11:58 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-09-15 09:57 UTCEG score recompute
  50. 2026-09-15 09:57 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  51. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-09-14 07:56 UTCEG score recompute
  53. 2026-09-14 07:56 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  54. 2026-09-13 05:55 UTCEG score recompute
  55. 2026-09-13 05:55 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  56. 2026-09-12 03:54 UTCEG score recompute
  57. 2026-09-12 03:54 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  58. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  59. 2026-09-11 01:53 UTCEG score recompute
  60. 2026-09-11 01:53 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  61. 2026-09-09 23:52 UTCEG score recompute
  62. 2026-09-09 23:52 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  63. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  64. 2026-09-08 20:52 UTCEG score recompute
  65. 2026-09-08 20:51 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  66. 2026-09-07 15:01 UTCEG score recompute
  67. 2026-09-07 15:01 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  68. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  69. 2026-09-06 12:38 UTCEG score recompute
  70. 2026-09-06 12:38 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8
  71. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  72. 2026-09-05 10:37 UTCEG score recompute
  73. 2026-09-05 10:37 UTCGHSA enrichmentGHSA-rrm3-x23q-98qc · GitHub severity HIGH · GitHub CVSS 6.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82020?
CVE-2026-82020 is a medium-severity vulnerability; its CVE record was published on August 28, 2026. Hermes Agent 0.16.0 prior to 0.17.0 contains an improper path restriction vulnerability that allows attackers who can influence ingested message content to overwrite the credential store by bypassing sensitive-path guards that excluded the auth.json file. Attackers can craft malicious messages…
When was CVE-2026-82020 made public?
CVE-2026-82020 was made public on June 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-82020 actively exploited?
CVE-2026-82020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82020?
CVE-2026-82020 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82020?
A fix for CVE-2026-82020 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82020 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82020

Explore →

Is Your Infrastructure Affected by CVE-2026-82020?

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

Book a Demo →Browse All CVEs