Categories
CVE-2026-9353 high CVSS 7.3

Vulnerability in hermes-agent (CVE-2026-9353)

Summary

Vulnerability in hermes-agent (CVE-2026-9353). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.15.0 or later.

Original description

The description as published by the source.

A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.23. Impacted is an unknown function of the file agent/skills_guard.py of the component Skills Guard Multi-Word Prompt Handler. The manipulation of the argument THREAT_PATTERNS leads to injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-9353 has been found in hermes-agent.
Risk of unauthorized operations or information disclosure. CVSS score: 7.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-9353" on the vendor's site.

CVE-2026-9353 (hermes-agent) — CWE-74 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / 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-74) exists in hermes-agent.

📍 Affected scope

Check the vendor advisory for the affected versions of hermes-agent.

🔥 Severity

Severity: High (CVSS 7.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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'hermes-agent' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で hermes-agent を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade hermes-agent to 0.15.0

    ステージング環境で 0.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip hermes-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.15.0"}]}]
PyPI hermes-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.15.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details