dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-43917

MEDIUM · 5.3 CVSS v4.0 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 →
59/100
Remediation priority · Elevated
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.19.0 and earlier, the protectedProcedure middleware only verifies the user is authenticated - it does NOT enforce organization scoping. Each endpoint must individually verify the resource's org matches the session's activeOrganizationId. This affects the following endpoints: allByType, killProcess, and removeDeployment in deployment.ts; delete in rollbacks.ts; create, one, update, remove, manualBackupPostgres, MySql, Mariadb, Mongo, Compose, WebServer, and listBackupFiles in backup.ts; list, one, delete, update, runManually, and restoreVolumeBackupWithLogs in volume-backups.ts; getNodes, removeWorker, addWorker, and addManager in cluster.ts; and create in mount.ts.

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.19.0 and earlier has an Insecure Direct Object Reference (IDOR) vulnerability where the protectedProcedure middleware only verifies user authentication but fails to enforce organization scoping. This allows authenticated users to access, modify, or delete resources belonging to other organizations by manipulating the session's activeOrganizationId. The vulnerability affects 17+ endpoints across deployment.ts, rollbacks.ts, backup.ts, volume-backups.ts, cluster.ts, and mount.ts.

MitigationImplement organization scoping validation in each affected endpoint by verifying the resource's organization matches the session's activeOrganizationId, or enhance the protectedProcedure middleware to automatically enforce organization-level authorization for all procedures.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installed Dokploy version
    Check your Dokploy installation's version by reviewing the package.json, docker image tag, or running 'dokploy --version' if the CLI is available
    Affected if Version is 0.19.0 or earlier (including any 0.x.x release prior to 0.19.0)
  2. Locate the protectedProcedure middleware
    Inspect the Dokploy source code in the middleware or hooks directory for the protectedProcedure implementation, typically found in the server/trpc directory
    Affected if The middleware only performs authentication validation without checking organization ownership before processing requests
  3. Review affected endpoint files
    Examine the source files deployment.ts, rollbacks.ts, backup.ts, volume-backups.ts, cluster.ts, and mount.ts in your installation for tRPC procedure definitions
    Affected if These files contain procedures that use the protectedProcedure middleware without explicit organization scoping checks
  4. Check for organization authorization logic
    Search for 'activeOrganizationId' validation in the affected endpoint handlers - look for checks that compare session.organizationId or activeOrganizationId against the requested resource's organization field
    Affected if No organization ID validation exists before returning or modifying resource data in these endpoints
  5. Test endpoint authorization behavior
    Using an authenticated account belonging to Organization A, attempt to access or modify a resource that belongs to Organization B through the affected API endpoints
    Affected if Requests succeed when accessing cross-organization resources, indicating the authorization bypass is present

You are affected if running Dokploy version 0.19.0 or earlier and the protectedProcedure middleware lacks organization scoping validation in the listed endpoint files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement organization scoping validation in each affected endpoint by verifying the resource's organization matches the session's activeOrganizationId, or enhance the protectedProcedure middleware to automatically enforce organization-level authorization for all procedures.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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