dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45633

CRITICAL · 9.9 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 →
100/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.26.6 and earlier, Dokploy contains a command injection vulnerability in the /docker-container-logs WebSocket endpoint. The tail and since parameters are not validated and are directly concatenated into shell commands, allowing authenticated users to execute arbitrary commands with root 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 confidence

Dokploy 0.26.6 and earlier contains a command injection vulnerability in the /docker-container-logs WebSocket endpoint where the 'tail' and 'since' parameters are not validated and are directly concatenated into shell commands. This allows any authenticated user to execute arbitrary commands with root privileges.

MitigationImplement strict input validation for 'tail' and 'since' parameters (restrict to numeric values only) and refactor to use safe APIs or parameterized commands instead of shell concatenation; consider running Docker containers as non-root users.

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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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
    Check for Dokploy running as a service, Docker container, or installed on the system (look for dokploy-related processes or services)
    Affected if Dokploy is installed and running in the environment
  2. Determine installed Dokploy version
    Access the Dokploy admin interface or check the running container/image tag to find the exact version number
    Affected if The installed version is 0.26.6 or earlier
  3. Verify WebSocket endpoint exposure
    Confirm that the /docker-container-logs WebSocket endpoint is accessible (check reverse proxy configs, firewall rules, or network accessibility)
    Affected if The WebSocket endpoint is externally or internally accessible without additional network restrictions
  4. Confirm authentication is required
    Test whether valid credentials are needed to access the /docker-container-logs endpoint (check if anonymous access is possible)
    Affected if The endpoint accepts authenticated requests, meaning attackers with valid accounts could exploit the flaw

A user is affected if they run Dokploy version 0.26.6 or earlier with the /docker-container-logs WebSocket endpoint accessible to authenticated users.

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

Implement strict input validation for 'tail' and 'since' parameters (restrict to numeric values only) and refactor to use safe APIs or parameterized commands instead of shell concatenation; consider running Docker containers as non-root users.

Recommended fix Moderate confidence

Latest Dokploy release after version 0.26.6 (check official Dokploy releases)

  1. 1. Backup your current Dokploy installation and database before upgrading
  2. 2. Upgrade Dokploy to the latest available version (after 0.26.6) by following the official upgrade documentation for your deployment method
  3. 3. After upgrading, verify the /docker-container-logs endpoint now properly validates and sanitizes the tail and since parameters
  4. 4. Confirm the WebSocket endpoint no longer concatenates user input directly into shell commands
  5. 5. Test the fix by attempting to use special characters in the tail and since parameters to ensure they are properly escaped or rejected
  6. 6. Review authentication controls to ensure only authorized users can access the /docker-container-logs endpoint
Caveat Review release notes for any breaking changes between 0.26.6 and the target version, particularly regarding Docker container management features

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45633 — 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-45633 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