dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-9367

HIGH · 7.3 CVSS v3.1 Published 2026-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in NousResearch hermes-agent up to 5157f5427f19488b31c6fdebbacd15d798ce7f63. This affects the function detect_dangerous_command of the file tools/approval.py of the component terminal_tool. This manipulation causes os command injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS command injection vulnerability in the terminal_tool component of NousResearch hermes-agent. The detect_dangerous_command function in tools/approval.py fails to properly sanitize inputs, allowing remote attackers to inject malicious OS commands.

MitigationImplement robust input validation and sanitization in the detect_dangerous_command function. Consider using parameterized commands or whitelist-based validation to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate hermes-agent installation
    Identify the directory where hermes-agent is installed. Common locations include /opt/hermes-agent, /usr/local/lib/hermes-agent, or a user-installed Python package location. Use 'pip show hermes-agent' or search for the hermes-agent directory structure.
    Affected if hermes-agent is present in the environment
  2. Identify terminal_tool component status
    Examine the hermes-agent configuration to determine if the terminal_tool component is enabled. Check configuration files (typically in a config/ or settings/ directory) for entries related to terminal_tool, shell_exec, or command_execution features.
    Affected if terminal_tool is enabled in the configuration
  3. Locate tools/approval.py
    Navigate to the tools/ directory within the hermes-agent installation and locate the approval.py file. The full path is typically [hermes-agent-root]/tools/approval.py.
    Affected if tools/approval.py exists in the hermes-agent installation
  4. Inspect detect_dangerous_command function
    Open tools/approval.py and locate the detect_dangerous_command function. Examine the function implementation for input validation or sanitization logic. Look for patterns such as regex checks, allowlists, or input stripping before command construction.
    Affected if the function lacks proper input validation/sanitization or uses insufficient validation methods (e.g., only checks for dangerous keywords without blocking all injection vectors)
  5. Check for command execution flow
    Trace how user input flows from external sources through detect_donagerous_command to actual OS command execution (e.g., subprocess calls, os.system, shell=True usage). Determine if unsanitized input can reach command execution points.
    Affected if user-supplied input can reach OS command execution without adequate validation through this function

A user is affected if hermes-agent with the terminal_tool component is installed and the detect_dangerous_command function in tools/approval.py lacks proper input sanitization, allowing arbitrary OS command injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust input validation and sanitization in the detect_dangerous_command function. Consider using parameterized commands or whitelist-based validation to prevent command injection.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9367 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data