CVE-2026-14625
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 · uneditedA security flaw has been discovered in NousResearch hermes-agent up to 0.15.2. The affected element is the function shell.exec of the file tui_gateway/server.py. The manipulation results in protection mechanism failure. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. 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 · moderate confidenceA command injection vulnerability exists in the shell.exec function within tui_gateway/server.py of NousResearch hermes-agent up to version 0.15.2. The function fails to properly sanitize user input, allowing remote attackers to bypass protection mechanisms and execute arbitrary shell commands.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify hermes-agent installation versionRun `pip show hermes-agent` or check the package version in your environment. If installed from source, check the version tag or changelog.Affected if Installed version is 0.15.2 or lower, or version cannot be determined but the product is NousResearch hermes-agent
-
Locate tui_gateway/server.py in the codebaseFind the file tui_gateway/server.py within the hermes-agent installation directory or source code repository.Affected if The file exists and is part of the installed hermes-agent version
-
Identify shell.exec usage in server.pySearch the file for occurrences of `shell.exec` function calls. Use `grep -n 'shell.exec' tui_gateway/server.py` or open the file and inspect.Affected if The file contains any shell.exec calls that process external input
-
Verify input sanitization on shell.exec callsExamine each shell.exec call to determine if user-supplied input (parameters, headers, request body data) is passed directly to the command without validation or escaping. Look for patterns where input variables are concatenated into shell commands.Affected if User-controlled input is passed to shell.exec without sanitization, validation, or use of safer alternatives
If hermes-agent version is 0.15.2 or lower AND tui_gateway/server.py contains shell.exec calls that handle external input without sanitization, the environment is vulnerable to command injection.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version if available; otherwise, implement strict input validation and sanitization on all shell.exec calls, preferably by replacing shell.exec with safer alternatives that avoid shell interpretation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14625 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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