Skip to main content
Menu
CVEs

CVE

Dokploy code execution via command injection in schedule appName

Affects Dokploy versions before 0.31.1, where a user who creates or updates a schedule can set the appName used by dokploy-server schedules. Fixed in 0.31.1.

CVE-2026-129985EUVD-2026-129322Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.31.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Dokploy versions before 0.31.1 (reported against v0.29.4) A user can create or update a schedule, which sets the appName The schedule type is dokploy-server, so the script runs on the Dokploy host

Summary

Dokploy, a self-hosted platform-as-a-service tool, has a command injection flaw in how it handles the appName of a schedule. A remote attacker with a low-privilege logged-in account who can create or update a dokploy-server schedule can run operating system commands when the schedule is saved, with the Dokploy process's privileges, which on typical installations includes root.

Original description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, a user-controlled schedule appName is joined into the schedule directory path and interpolated without shell quoting into commands that create the directory and write the schedule script. An authenticated user who can create or update a dokploy-server schedule can inject operating-system commands that execute with the Dokploy process privileges when the schedule is saved, including root privileges on typical installations. This issue is fixed in version 0.31.1.

Who should check

Teams running self-hosted Dokploy versions before 0.31.1 where members can create or update dokploy-server schedules.

“When creating or updating a schedule in Dokploy, the appName can be provided by the user.”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Dokploy versions before 0.31.1 (reported against v0.29.4) A user can create or update a schedule, which sets the appName The schedule type is dokploy-server, so the script runs on the Dokploy host
  • Upgrade to a fixed version: 0.31.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129985 (Dokploy: RCE via Command Injection in Schedule appName), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129985 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: fixed in 0.31.1
Fixed versions: 0.31.1.
Conditions (all must be true for the bug to be hit):
- Dokploy versions before 0.31.1 (reported against v0.29.4) (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-8m32-h7qx-8r79)
- A user can create or update a schedule, which sets the appName (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-8m32-h7qx-8r79)
- The schedule type is dokploy-server, so the script runs on the Dokploy host (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-8m32-h7qx-8r79)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129985 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129985 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-8m32-h7qx-8r79
- https://github.com/Dokploy/dokploy/pull/5906
- https://github.com/Dokploy/dokploy/commit/0fa3101a7e76173c60a3015d37a02e7c892b9ab3
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129985
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129985"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Dokploy dokploy

    fixed in 0.31.1

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Dokploy/dokploy · Advisory GHSA-8m32-h7qx-8r79
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129985
RecordNVD · CVE-2026-129985
Other links 3
RepositoryGitHub · Dokploy/dokploy · Pull request #5906
RepositoryGitHub · Dokploy/dokploy · Commit 0fa3101a
RepositoryGitHub · Dokploy/dokploy · Release v0.31.1

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129985

Is CVE-2026-129985 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A user-supplied appName in a schedule is used in a script that runs on the Dokploy host. This lets arbitrary operating-system commands run with root-level access, which the advisory says can lead to full system compromise.Source: github.com

Which versions are affected by CVE-2026-129985?

dokploy: before 0.31.1.Source: cve.now feed data

Am I affected, and how do I check?

Dokploy versions before 0.31.1 are affected; the advisory reports it against v0.29.4. The relevant setup is schedules of type dokploy-server, where the script runs on the Dokploy host. Check the installed Dokploy version and whether any schedules use that type.Source: github.com

How do I fix CVE-2026-129985?

Upgrade Dokploy to 0.31.1 or later, which is the fixed version listed for this vulnerability.Source: github.com

More CVEs