Komodo Periphery 2.2.0 flaw lets users execute root commands via container names

An attacker with a basic user account on a Komodo server can now execute arbitrary commands as root on the host machine. This privilege escalation occurs because the Periphery agent fails to validate Docker container names before using them in shell commands. The flaw allows users to inject malicious code through standard operations like deleting containers or searching logs. Once executed, these commands run with the highest system privileges, giving the attacker full control over the underlying server.

In plain English

The Komodo platform uses an agent called Periphery to manage Docker environments on servers. In versions up to 2.2.0, this agent takes user-supplied container names and inserts them directly into shell commands without checking for dangerous characters. This means a user can craft a container name that includes shell metacharacters, effectively tricking the agent into running whatever code they append. The result is that a low-privilege user gains the same power as the system administrator.

The background

Komodo is an open-source server management tool maintained by mogh.tech, popular in self-hosted and multi-server setups. The vulnerability was reported to CERT/CC by researcher Muhammadjon Ahmadjonov. The advisory notes that the flaw affects two specific operations: container destruction and container log searches. In both cases, raw input is passed to `sh -c` without escaping. This issue is distinct from the pypdftk library flaw RedTeam Monitor reported on 2026-10-14, which involved PDF processing rather than container management.

What changes now

The vendor has released version 2.3.0, which fixes the validation issue. CERT/CC advises all users to update immediately to remediate the risk. The advisory clarifies that only installations with multiple users, where non-admin users have restricted permissions, are affected. Single-admin setups are not vulnerable because admin users already possess full access. Unauthenticated attackers cannot exploit this flaw unless the Periphery instance is exposed directly without its passkey protection.

What made it possible

This incident illustrates the risks of unsanitized input in shell command construction. When applications interpolate user data into system commands without proper escaping, they create injection vectors. This weakness typically serves the privilege escalation stage of an intrusion, allowing a low-privileged account to bypass intended restrictions. Teams usually monitor for unexpected command execution patterns in agent logs. Check whether your environment validates all user-supplied identifiers before passing them to shell interpreters. Ensure that permission models strictly limit what non-admin users can trigger.

What to do and how to stay safe: Komodo

• Update the Komodo Periphery agent to version 2.3.0 or higher to apply the vendor's fix.
• Audit user accounts to ensure non-admin users do not have unnecessary permissions on container resources.
• Monitor server logs for unexpected command executions or unusual container deletion and log search activity.
• Verify that Periphery instances are not exposed directly to untrusted networks without passkey authentication.

Step-by-step guide: Automatic Updates Mistakes That Leave Systems Exposed

General security guidance from the RedTeam Monitor newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Can unauthenticated attackers exploit this vulnerability?

No, exploitation requires an authenticated account with specific grants, such as Logs or Execute permissions on a resource.

Does this affect single-user Komodo installations?

No, the advisory states that installations with only admin users are not affected because admins already have full access.

What version of Periphery fixes the issue?

The vulnerability is remediated in version 2.3.0 and higher; versions 2.2.0 and earlier are vulnerable.