CVE-2026-45629
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 /listen-deployment WebSocket endpoint allows any organization member to execute arbitrary system commands on remote servers managed by Dokploy, leading to full server compromise.
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.28.8 and earlier contain an authenticated OS command injection vulnerability in the /listen-deployment WebSocket endpoint. Any authenticated organization member can inject and execute arbitrary system commands on remote servers managed by the Dokploy PaaS, enabling full server compromise.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Dokploy installationCheck if Dokploy is running in your environment by looking for Dokploy containers, services, or the Dokploy dashboard URL. Inspect running containers with 'docker ps' or check for Dokploy-related processes.Affected if Dokploy is installed and running in the environment
-
Check Dokploy versionAccess the Dokploy dashboard or API to determine the installed version. Typically found in the admin settings or by querying the Dokploy container/service version endpoint. Compare against the affected range (versions prior to 0.28.8).Affected if Dokploy version is 0.28.8 or earlier
-
Verify /listen-deployment endpoint exposureInspect your Dokploy configuration or API gateway to confirm the /listen-deployment WebSocket endpoint is accessible. Check routing rules, reverse proxy configs, or API definitions for this specific endpoint.Affected if The /listen-deployment WebSocket endpoint is exposed and reachable
-
Review organization member permissionsCheck the Dokploy admin panel or user management system to enumerate organization member roles and permissions. Verify if standard members have access to deployment-related features.Affected if Organization members have access to deployment functionality or server management features
-
Confirm remote server management configurationExamine Dokploy settings to see if remote servers are configured for deployment. Check the servers panel or infrastructure configuration for any managed remote hosts.Affected if Remote servers are configured and managed through the Dokploy platform
You are affected if Dokploy is running with version 0.28.8 or earlier AND the /listen-deployment WebSocket endpoint is accessible to organization members who can trigger command execution on managed remote servers.
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 version newer than 0.28.8 as soon as a patch is released. Until then, restrict organization membership to trusted users only and consider network-segmenting Dokploy-managed servers.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45629 — 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-45629 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