dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45632

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.7 and earlier, the schedule router does not enforce organization/role checks. As a result, any authenticated user can create, update, run, or delete schedules belonging to other organizations if they know the scheduleId/serverId. Schedule types server and dokploy-server write and execute scripts on the host or remote servers, enabling RCE on the Dokploy host or a target server.

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.7 and earlier contains an IDOR vulnerability in the schedule router where organization/role access controls are not enforced. Any authenticated user can create, update, run, or delete schedules belonging to other organizations by providing the scheduleId/serverId. Since 'server' and 'dokploy-server' schedule types write and execute scripts on the host or remote servers, this allows unauthenticated (in terms of authorization) users to achieve remote code execution on the Dokploy host or target servers.

MitigationImplement proper organization-based and role-based access control (RBAC) checks in the schedule router to ensure users can only access schedules within their own organization. Validate that the authenticated user's organization matches the schedule's organization before allowing any operations.

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 version
    Check the installed Dokploy version through the admin UI, API endpoint, or docker container tags. Compare against 0.26.7 (vulnerable if 0.26.7 or earlier).
    Affected if Installed version is 0.26.7 or earlier.
  2. Confirm user authentication is enabled
    Verify that Dokploy's authentication system is active and user accounts exist. The vulnerability affects authenticated users, so unauthenticated access alone does not trigger this flaw.
    Affected if User authentication is enabled and at least one user account exists.
  3. Locate existing schedule resources
    Query the schedules API or database to list all defined schedules in the system. Identify schedules with type 'server' or 'dokploy-server'.
    Affected if Any schedule exists, particularly those using 'server' or 'dokploy-server' types that enable script execution.
  4. Test cross-organization schedule access
    Using a test user account from one organization, attempt to directly reference a scheduleId or serverId belonging to a different organization via API request.
    Affected if The request succeeds and returns schedule details or allows operations on schedules outside the user's organization.

The environment is affected if running Dokploy 0.26.7 or earlier with authentication enabled and schedules (especially server/dokploy-server types) exist, where users can access schedules from other organizations.

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 proper organization-based and role-based access control (RBAC) checks in the schedule router to ensure users can only access schedules within their own organization. Validate that the authenticated user's organization matches the schedule's organization before allowing any operations.

Recommended fix Moderate confidence

Upgrade to the latest stable Dokploy release (version 0.26.8 or later)

  1. 1. Identify the current Dokploy version by checking the deployment configuration or running `dokploy --version`
  2. 2. If running version 0.26.7 or earlier, upgrade to a version after 0.26.7 where the authorization fix is included
  3. 3. Review and rotate any credentials or API keys that may have been exposed if the vulnerability was exploited
  4. 4. Audit logs for any unauthorized schedule creations, updates, or executions that may indicate exploitation
  5. 5. After upgrading, verify that organization/role checks are enforced by testing cross-organization schedule access attempts
Caveat Review release notes for any breaking changes between your current version and the target upgrade version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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