Horizon Alert
Summary of the vulnerability and why it matters
A critical vulnerability in Dokploy, a self-hosted Platform as a Service, could allow an authenticated user to execute arbitrary commands on the host system. This impacts the integrity and availability of services managed through Dokploy, as an attacker could gain root-level control. The issue arises from how backup configurations are handled, potentially leading to significant operational disruption if exploited.
- Unauthenticated commands executed via backup settings.
- Critical remote control risk for managed systems.
- Confirm Dokploy relevance and assess exposure.
Attack Path
How an attacker could exploit the issue
An attacker with organizational membership and backup permissions could exploit this vulnerability. By providing specially crafted input in the backup prefix field, they can manipulate commands executed during backup or cleanup operations. This could allow them to run arbitrary commands with root privileges on the Dokploy host or connected remote servers, potentially leading to a full system compromise.
- Authenticated user, backup permission required.
- Malicious input in backup prefix field.
- Arbitrary command execution as root.
Live Threat
Current exploitation, exposure, and threat context
An authenticated organization member with backup permissions could execute arbitrary commands as root on the Dokploy host or a configured remote server. This could occur when backups are manually initiated, run on a schedule, or during retention cleanup, potentially impacting the integrity and availability of the host system and its data.
- Root command execution on hosts.
- Backup operations trigger command injection.
- System compromise and data loss.
Operational Fix
Recommended remediation, mitigation, and detection steps
Application owners, platform teams, and infrastructure teams are likely responsible for addressing this vulnerability within their self-hosted Dokploy instances. The first practical step is to identify all Dokploy deployments, confirm their network accessibility and business criticality, and then determine the accountable team for remediation planning and execution.
- Identify affected Dokploy instances and owners.
- Verify backup configurations and network exposure.
- Plan remediation based on identified risk.