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.
CVE-2026-82020
MEDIUMPre-NVD 6.86.8—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. the CNA's CVSS baseline 6.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, ghsa
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity68% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 29, 2026
Advisory Details (5)
Auto-updated Aug 28, 2026Patch available. Sources: github_release, github_pr, github_commit.
generic
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-toolgithub_commit
commit 2b67e96aec2a (NousResearch/hermes-agent)
Fix landed in NousResearch/hermes-agent commit 2b67e96aec2a — awaiting tagged release
https://github.com/NousResearch/hermes-agent/commit/2b67e96aec2aa2abd5e94b544cda8e564c75f9f5github_commit
commit da28d5d11395 (NousResearch/hermes-agent)
Fix landed in NousResearch/hermes-agent commit da28d5d11395 — awaiting tagged release
https://github.com/NousResearch/hermes-agent/commit/da28d5d113956dcf803d5cff552a120740a96a59github_pr
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/45821github_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.19Vendor 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 6× in last 7d / 6× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 11:58 UTCEG score recompute
- 2026-08-29 11:58 UTCGHSA enrichment
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 19:38 UTCEG score recompute
- 2026-08-28 19:36 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82020?
CVE-2026-82020 is a medium vulnerability 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 disclosed?
CVE-2026-82020 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82020 actively exploited?
CVE-2026-82020 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 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-82020?
CVE-2026-82020 has a CVSS v4.0 base score of 6.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-82020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82020, 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
Explore the affected products and dependency analysis for CVE-2026-82020
Is Your Infrastructure Affected by CVE-2026-82020?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.