CVE-2026-27130: Dokploy has Command Injection in its Service Operations

Published May 18, 2026
·
Updated

Dokploy is a free, self-hostable Platform as a Service (PaaS). Versions 0.26.6 and below have OS command injection through the appName parameter. 3 chained issues cause this problem: inadequate input sanitization, lack of schema validation and direct shell interpolation. User-controlled application names are passed through inadequate sanitization (cleanAppName function only replaces spaces and converts to lowercase) before being interpolated directly into shell commands executed via execAsync() and execAsyncRemote(). An authenticated attacker can inject shell metacharacters (e.g., ;, $(), backticks, |, &) in the appName field during application creation, which are then executed with server-level privileges when service operations (start, stop, remove, scale) are triggered. This issue has been resolved in version 0.26.7.

Affected Software

1 affected component
Dokploy Dokploy<=0.26.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Dokploy to a version that resolves this vulnerability.

    Fixed in 0.26.7
  2. Configuration

    Ensure user-controlled application names (appName) are properly sanitized and not interpolated directly into shell commands executed by execAsync() / execAsyncRemote() during service operations (start, stop, remove, scale). The reported issue is that cleanAppName() only replaces spaces and converts to lowercase, which is insufficient.

    Dokploy service operations (execAsync/execAsyncRemote) appName interpolation into shell commands = sanitize and avoid direct shell interpolation (e.g., do not interpolate user-controlled appName into shell metacharacter-sensitive command strings)

Event History

May 18, 2026
CVE Published
via MITRE·08:58 PM
Data Sourced
via MITRE·08:58 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-27130?

CVE-2026-27130 has a high severity due to the potential for command injection that can lead to unauthorized access and system compromise.

2

How do I fix CVE-2026-27130?

To fix CVE-2026-27130, upgrade Dokploy to version 0.26.7 or later, where the command injection vulnerability has been addressed.

3

What versions of Dokploy are affected by CVE-2026-27130?

CVE-2026-27130 affects all Dokploy versions up to and including 0.26.6.

4

What are the risks associated with CVE-2026-27130?

The risks include the potential execution of arbitrary commands on the server, leading to data compromise and service disruption.

5

Is input sanitization sufficient to mitigate CVE-2026-27130?

No, input sanitization alone is not sufficient; a combination of schema validation and proper coding practices is necessary to fully mitigate the risks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203