dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45662

HIGH · 8.8 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.0 and earlier, the deleteRegistry function in Dokploy (packages/server/src/services/registry.ts) executes docker logout ${response.registryUrl} without shell escaping. In the same file, the docker login command correctly uses shEscape() to prevent command injection. This inconsistency creates a command injection vulnerability when deleting a registry with a crafted registryUrl.

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 confidence

In Dokploy 0.29.0 and earlier, the deleteRegistry function in registry.ts executes `docker logout ${response.registryUrl}` without shell escaping, allowing command injection via a crafted registryUrl. The same file correctly uses shEscape() for the docker login command, demonstrating this protection was known but inconsistently applied.

MitigationApply shEscape() to the registryUrl parameter in the deleteRegistry function before constructing the docker logout command, matching the existing secure pattern used for docker login.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dokploy installation version
    Check the installed Dokploy version by reviewing package.json, a version file, or the admin UI if accessible. Compare against the affected range: 0.29.0 and earlier.
    Affected if The installed version is 0.29.0 or any version prior to 0.29.0.
  2. Locate the deleteRegistry function source
    Inspect the file packages/server/src/services/registry.ts in the Dokploy installation directory. Look for the deleteRegistry function definition.
    Affected if The file exists and contains a deleteRegistry function that executes docker logout.
  3. Verify shell escaping on registryUrl parameter
    Within the deleteRegistry function, examine the line that executes 'docker logout'. Check whether the registryUrl variable is wrapped with shEscape() or any equivalent sanitization function before being passed to the command.
    Affected if The docker logout command uses registryUrl directly without passing it through shEscape() or equivalent escaping, while the docker login command in the same file uses shEscape().
  4. Review for vulnerable string interpolation pattern
    Search the deleteRegistry function for the pattern 'docker logout ${' to confirm the command is being built using template literal interpolation of the registryUrl parameter.
    Affected if The code constructs the docker logout command using template literals with unescaped variable interpolation (e.g., `docker logout ${registryUrl}`).
  5. Audit docker command execution logs
    Review server logs, audit trails, or docker daemon logs for any registry deletion operations. Look for docker logout commands with unusual or suspicious URL patterns containing shell metacharacters.
    Affected if Historical or current logs show docker logout commands with registryUrl values containing characters like ;, |, &, $, or backticks.

A user is affected if running Dokploy version 0.29.0 or earlier and the deleteRegistry function uses template literal interpolation for registryUrl in the docker logout command without applying shEscape() or equivalent input sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply shEscape() to the registryUrl parameter in the deleteRegistry function before constructing the docker logout command, matching the existing secure pattern used for docker login.

Recommended fix Moderate confidence

Dokploy version greater than 0.29.0 (check GitHub releases for the actual fixed version)

  1. 1. Locate the file `packages/server/src/services/registry.ts` in the Dokploy server codebase.
  2. 2. Find the `deleteRegistry` function that executes `docker logout ${response.registryUrl}`.
  3. 3. Apply `shEscape()` to the `response.registryUrl` variable, similar to how it is used in the `docker login` command in the same file.
  4. 4. The corrected command should look like: `docker logout ${shEscape(response.registryUrl)}`.
  5. 5. Commit and deploy the patched version.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45662 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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