← Back
CVE-2026-53870
medium
CVSS 5.5
Vulnerability in hermes-agent (CVE-2026-53870)
Summary
vulnerability in hermes-agent (CVE-2026-53870). Confidential information can be exposed externally. Mitigation: upgrade to `0.16.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53870** has been found in hermes-agent.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade hermes-agent to **0.16.0** or later.
If unsure, ask your IT team or search "hermes-agent CVE-2026-53870" on the vendor's site.
CVE-2026-53870 (hermes-agent) — CWE-276 / CVSS v3 5.5
Attack vector: local / no user interaction
Patched: `0.16.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-276) exists in hermes-agent.
📍 Affected scope
hermes-agent — .
🔥 Severity
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.16.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'hermes-agent' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'hermes-agent' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `hermes-agent` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade hermes-agent to 0.16.0ステージング環境で 0.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
hermes-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.0"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-53870
- web https://github.com/NousResearch/hermes-agent/pull/30917
- web https://github.com/NousResearch/hermes-agent/pull/31469
- web https://github.com/NousResearch/hermes-agent/commit/3bace071bfadf2d2bec2ee048471a31ec920e3e8
- web https://github.com/NousResearch/hermes-agent/releases/tag/v2026.6.5
- web https://www.vulncheck.com/advisories/hermes-agent-sensitive-file-permission-vulnerability-in-store-files
- web https://github.com/advisories/GHSA-99f9-j8r3-p853