CVE-2026-45628
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.2 and earlier, Dokploy constructs shell commands using JavaScript template literals and executes them via child_process.exec() (which runs through /bin/sh -c). User-supplied branch names, repository URLs, and Docker credentials are interpolated directly into these commands without escaping. This requires an authenticated user with application create/edit privileges.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDokploy versions 0.29.2 and earlier are vulnerable to command injection because the application constructs shell commands using JavaScript template literals and executes them via child_process.exec() (which invokes /bin/sh -c). Authenticated users with application create/edit privileges can supply malicious branch names, repository URLs, or Docker credentials containing shell metacharacters that get interpolated directly into commands without escaping, achieving arbitrary command execution on the host.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Dokploy versionRun `npm list dokploy` or check the package.json in the Dokploy installation directory, or use the Dokploy CLI if available to query the versionAffected if The installed version is 0.29.2 or earlier
-
Identify child_process.exec usage with template literalsSearch the Dokploy source code for patterns like `child_process.exec(` followed by template literals (`${`) that may contain user-supplied variables such as branch names, repository URLs, or Docker credentialsAffected if The codebase contains child_process.exec() calls that interpolate user input directly into shell command strings
-
Verify application create/edit endpoints existCheck if the Dokploy web interface or API exposes endpoints for creating or editing applications, typically under routes related to 'application', 'project', or 'deploy'Affected if Application create/edit functionality is accessible to authenticated users
-
Confirm authentication is enabledReview Dokploy authentication settings or configuration to verify that user authentication is required for accessing application management featuresAffected if Authentication is disabled or allows untrusted users to access application create/edit privileges
A user is affected if they run Dokploy version 0.29.2 or earlier with authentication enabled and the application create/edit feature exposed to users who can supply branch names, repository URLs, or Docker credentials containing shell metacharacters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of Dokploy. Until a patch is available, implement strict allowlist-based input validation for branch names, repository URLs, and Docker credentials, and refactor command construction to avoid shell interpretation (e.g., use array-based execFile arguments or a proper command-builder library).
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45628 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data