← Back
CVE-2026-9369
medium
CVSS 5.3
Vulnerability in hermes-agent (CVE-2026-9369)
Summary
vulnerability in hermes-agent (CVE-2026-9369). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.15.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-9369** has been found in hermes-agent.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade hermes-agent to **0.15.0** or later.
If unsure, ask your IT team or search "hermes-agent CVE-2026-9369" on the vendor's site.
CVE-2026-9369 (hermes-agent) — CWE-697 / CVSS v3 5.3
Attack vector: local / no user interaction
Patched: `0.15.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-697) exists in hermes-agent.
📍 Affected scope
hermes-agent — .
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.15.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.15.0ステージング環境で 0.15.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.15.0"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-9369
- web https://gist.github.com/YLChen-007/062b77ceac6aa9844842a616f5d2ef30
- web https://vuldb.com/submit/812230
- web https://vuldb.com/vuln/365332
- web https://vuldb.com/vuln/365332/cti
- web https://github.com/advisories/GHSA-cv5c-mh6j-wvp9
- web https://github.com/NousResearch/hermes-agent/commit/09f85f2cf79362a2f7963754b49a44cb3d234176