CVE-2026-45630
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.28.8 and earlier, authenticated OS command injection in the application.updateTraefikConfig tRPC endpoint allows admin/owner users to execute arbitrary system commands on remote servers via unsanitized echo shell interpolation.
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 · moderate confidenceDokploy before version 0.28.8 contains an authenticated OS command injection vulnerability in the application.updateTraefikConfig tRPC endpoint. Admin or owner users can execute arbitrary system commands on remote servers due to unsanitized echo shell interpolation in the Traefik configuration update functionality.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
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.
-
Confirm Dokploy installationLocate Dokploy installation directory or check running containers: 'docker ps | grep dokploy' or 'kubectl get pods -A | grep dokploy' if using KubernetesAffected if Dokploy is not installed on the system
-
Identify Dokploy versionCheck installed Dokploy version via package.json, Docker image tag, or 'dokploy --version' command if CLI availableAffected if Running any version of Dokploy with the vulnerable endpoint exposed
-
Verify admin/owner user accessReview user roles in Dokploy admin panel or database: check 'users' or 'members' table for role='admin' or role='owner' accountsAffected if Admin or owner user accounts exist with access to the tRPC API
-
Check updateTraefikConfig endpoint exposureInspect tRPC router configuration in Dokploy source code for 'application.updateTraefikConfig' procedure definition and verify it is exposed without additional authentication layersAffected if The endpoint is accessible to authenticated admin/owner users
-
Identify vulnerable shell interpolation patternSearch Dokploy codebase for patterns like 'echo ${variable}' or 'echo $variable' inside shell commands within the updateTraefikConfig handler, particularly where user input flows into these commandsAffected if User-supplied parameters from updateTraefikConfig are passed directly to shell commands without sanitization
A user is affected if Dokploy is running, they have admin/owner access, and the updateTraefikConfig endpoint processes user input through unsanitized shell interpolation.
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 dataUpdate Dokploy to version 0.28.9 or later. Until a patch is available, restrict admin/owner account access, implement network segmentation, and audit existing admin accounts for compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45630 — 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-45630 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