# CVE-2026-110005: Moghtech Komodo contains an OS command injection vulnerability

> Authenticated low-privileged users can execute arbitrary root commands on managed hosts via shell metacharacters in container names.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-hxg3-3gpg-5m9c

## What is CVE-2026-110005?

CVE-2026-110005 is a high-severity command injection vulnerability in Komodo, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The `periphery` agent's container-management functionality of Komodo version 2.2.0 contains an OS command injection vulnerability. An authenticated low-privileged user with `Execute`, or `Read` plus `Logs`, permission on a managed server can supply shell metacharacters in a container name processed by the `DestroyContainer` or `SearchContainerLog` operations. The container name is interpolated without escaping into a command executed using `sh -c`, allowing arbitrary commands to execute as root on the managed host. This permits a user without Komodo's `Terminal` permission to obtain unrestricted host-level command execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-110005?


## How do I fix CVE-2026-110005?

No fix has been published for CVE-2026-110005 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110005 being exploited?

There is no known exploitation of CVE-2026-110005 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110005 and fix it if it is affected.

What it is: CVE-2026-110005 is a high-severity command injection vulnerability in Komodo, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110005 in the wild and no public exploit code.

Affected product: Komodo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110005/ (Markdown: https://insights.sbomify.com/CVE-2026-110005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110005
- OSV: https://osv.dev/vulnerability/CVE-2026-110005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110005/
Summaries are generated and may contain mistakes; the official description above is the record.