CERT/CC advisory VU#456950 covers Komodo Periphery command injection flaw
2 companies named across 2 categories, one of 2 articles referencing VU. Previous coverage: AI training portals, cloud sandboxes, and security advisories - Week of September 28, 2026 (Sep 2026).
Best suited for
- Seniority
- Staff
- Job function
- Cybersecurity / Information Security
- Persona
- Platform / Infrastructure Engineer
- Buyer role
- Technical Implementer / Administrator
- Decision stage
- Post Buy
- Adoption curve
- Early Majority
- Technology maturity
- Established Technology
- Industry
- Information Technology / Cloud & Infrastructure Software / Cloud Infrastructure, Automation & Platform Engineering / Container Management & Kubernetes
Our classification, not the publisher's statement. Best suited for, not only for.
Periphery, an agent service within the open-source Komodo server and deployment manager, contains an OS command injection vulnerability that can let an authenticated attacker run arbitrary commands on the underlying host.
Versions less than or equal to 2.2.0 are affected, tracked as CVE-2026-110005. Periphery does not properly validate user-supplied Docker container names before inserting them into sh -c shell commands. Two operations carry the flaw: container destruction, through DestroyContainer and RemoveContainer, and container log searches, through SearchContainerLog and GetContainerLogSearch. Raw container names are placed directly into these command lines without shell escaping or validation, and the commands run with root privileges on the host OS and the Docker socket.
An authenticated non-admin user can escalate privileges through OS command injection by supplying a maliciously crafted container name. Successful exploitation enables arbitrary command execution as root on a target server within a Komodo deployment. This can allow an attacker to establish persistence, achieve lateral movement, and completely compromise the managed infrastructure of a user or organization.
Komodo was contacted to coordinate this vulnerability, and a patch has been implemented to remediate the issue in versions 2.3.0 and higher.
CERT/CC advises all users to update without delay. Muhammadjon Ahmadjonov is credited with reporting the vulnerability.
Blog post, originally published by Alex Lewis at kb.cert.org.