Software Engineering Institute

Notified:  2026-08-19 Updated: 2026-10-13

Statement Date:   August 19, 2026

CVE-2026-110005

Affected

Vendor Statement

Who this affects

Only Komodo installations with more than one user, where non-admin users hold restricted permissions. This is a privilege escalation within Komodo's permission model — it is not remotely exploitable without an account, and it grants an admin nothing they do not already have. If your installation has only admin users, you are not affected.

Summary

Several Komodo Periphery handlers interpolated request-supplied values into shell command strings executed via bash -c without escaping them. An authenticated user with a Logs grant on a resource could inject shell metacharacters and execute arbitrary commands on the server hosting it.

Affected methods

Log search: SearchContainerLog, SearchStackLog, and the Swarm service equivalent require PermissionLevel::Read plus the Logs specific permission on a Server, Stack, or Deployment. Both the container/service name and the search terms were interpolated into a docker logs … | grep … pipeline. The terms sat inside hand-written single quotes, so a term containing ' escaped its quoting and ran as a separate command.

RunStackService: Requires PermissionLevel::Execute on a Stack. The ad-hoc supplied service, workdir, user, entrypoint, and env were interpolated into docker compose run (only command was escaped).

Swarm secret/config creation left name, driver, and labels unescaped and passed the payload through a <<'EOF' heredoc, so a payload containing a line of exactly EOF closed it early and executed the following lines. Handlers on the non-shell execution path could not execute commands, but a name beginning with - was still parsed as a flag by docker.

Impact

Arbitrary command execution as the Periphery process user on the target server, bypassing the Komodo permission model.

Exploitation requires an account holding one of the grants above. An account with no relevant grant, or an unauthenticated attacker, cannot reach these endpoints — unless a Periphery instance is exposed directly without its passkey.

Affected versions

All versions prior to 2.3.0. Verified vulnerable at v1.19.1, v2.0.0, v2.1.0, v2.1.1, v2.1.2, and v2.2.0. The log search vector dates to the introduction of Stack support; RunStackService was introduced in v1.19.1.

Patches

Fixed in 2.3.0: request-supplied values are shell-escaped, the heredoc is replaced with a pipe, and -- precedes positional arguments to block argument injection.

Configuration fields documented to accept shell syntax (deployment command/extra_args, pre_deploy/post_deploy, on_clone/on_pull, compose_cmd_wrapper) are still passed to a shell by design; setting them requires write permission, which already implies command execution.

Workarounds

None. Auditing who holds Logs or Execute grants limits exposure but does not remove it. Upgrade to 2.3.0.

Classification

CWE-78: Improper Neutralization of Special Elements used in an OS Command
Secondary: CWE-88 (argument injection)
CVSS 3.1: 9.9 Critical — AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H