/

CVE-2026-72875

Severity:

HIGH RISK

(8.8)

OS Command Injection (CWE-78) in Dokploy Platform

CVE-2026-72875

Received

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-78

Impact:

Arbitrary Command Execution

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A command injection vulnerability in Dokploy allows shell commands to be executed on a managed server when a user with permission to read Traefik files supplies a crafted configuration path.

The issue becomes risky when user-controlled path data reaches a shell command without strict validation or safe argument handling.

Affected context

The vulnerability occurs in Dokploy's Traefik configuration-reading workflow when the path accepted by the settings API is passed to a remote shell command. Deployments are exposed when an authenticated user has the traefikFiles.read permission and the application does not constrain the path to approved files or avoid shell interpretation.

Exploit preconditions

  • Attack surface: Dokploy settings API and managed-server Traefik configuration access
  • Required access: An authenticated user with traefikFiles.read permission
  • Trigger point: Processing a user-influenced configuration path through the Traefik file-reading operation
  • Why exploitation is possible: The path is interpolated into a shell command, allowing shell metacharacters to alter command interpretation

Why this happens

The underlying flaw is an OS command injection caused by incorporating externally influenced path data into a shell command without using safe argument boundaries or sufficiently strict validation.

This maps to CWE-78: Improper Neutralization of Special Elements used in an OS Command, because input that should represent a file path can instead influence shell parsing and command execution.

Potential impact

  • An attacker may execute arbitrary commands on a managed server
  • Server credentials, application data, or deployment secrets could be exposed
  • The affected host could be modified, disrupted, or used for lateral movement
  • Running services and deployed workloads could be tampered with

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from file access operations and reducing trust in request-controlled paths.

Common defensive patterns include:

  • Use direct file APIs or process-spawn interfaces with argument arrays instead of shell-interpolated commands
  • Restrict paths to an allowlisted directory and approved filenames
  • Canonicalize and validate paths before access, while preventing traversal outside intended locations
  • Treat permission checks as necessary but insufficient input protection
  • Run managed-server agents and related services with least privilege
  • Limit accessible secrets, filesystem locations, and administrative capabilities
  • Apply secure-by-default input validation and centralized command-execution policies

How teams detect issues like this

Detection can include:

  • Static analysis for shell execution APIs receiving concatenated or interpolated request data
  • Code review checks for command strings constructed with paths, filenames, or query parameters
  • Taint analysis tracing API input into remote execution helpers
  • Runtime logging of command-execution requests, rejected paths, and unusual Traefik file access
  • Policy enforcement that prohibits shell-based file reads when direct filesystem APIs are available
  • Automated security review tools configured to identify CWE-78 patterns

Sources

SourceLink
github.comgithub.com/Dokploy/dokploy/commit/92310ddb143c8e67ca95eb7db661838a76579f2e
github.comgithub.com/Dokploy/dokploy/pull/4873
github.comgithub.com/Dokploy/dokploy/releases/tag/v0.29.13
github.comgithub.com/Dokploy/dokploy/security/advisories/GHSA-j3pv-r5wg-235m

Frequently asked

questions

It can be exploitable through the Dokploy API when the affected endpoint is reachable and the attacker has the required permission. The command executes on the relevant managed server rather than necessarily on the attacker's device.

The attacker needs authenticated access associated with the traefikFiles.read permission, subject to the deployment's authorization and network controls.

Avoid passing user-controlled values through a shell. Use direct file APIs or safely parameterized process execution, combined with strict allowlisting and path validation.

Apply least privilege, centralize and review command execution, perform taint-aware static analysis, and enforce policies that block shell interpolation of request-controlled data.

Find out what's already
exploitable in your codebase.