dbcve.org
DokployApplication

CVE-2025-53825

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-14
Fix available
A fix is available. Upgrade to 0.24.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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). Prior to version 0.24.3, an unauthenticated preview deployment vulnerability in Dokploy allows any user to execute arbitrary code and access sensitive environment variables by simply opening a pull request on a public repository. This exposes secrets and potentially enables remote code execution, putting all public Dokploy users using these preview deployments at risk. Version 0.24.3 contains a fix for the issue.

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 prior to 0.24.3 contains an unauthenticated vulnerability in its preview deployment feature. When a pull request is opened on a linked public repository, the system automatically deploys a preview environment without requiring authentication. This allows any external user to trigger the preview deployment, which exposes sensitive environment variables and secrets, and enables arbitrary code execution on the Dokploy server.

MitigationUpgrade Dokploy to version 0.24.3 or later. Until patched, avoid connecting public repositories with the preview deployment feature enabled, as unauthenticated attackers can exploit this to access secrets and execute arbitrary code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DokployApplication
Affected:< 0.24.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Dokploy version
    Locate the Dokploy installation and determine its version number. This may be found in the application UI, in a configuration file, or via a CLI command provided by Dokploy.
    Affected if The installed version is lower than 0.24.3.
  2. Identify connected repositories
    Review the Dokploy configuration to list all repositories linked to the Dokploy instance. Look for any repositories marked as public or accessible without authentication.
    Affected if One or more public repositories are connected to Dokploy.
  3. Verify preview deployment feature status
    Locate the preview deployment feature configuration within Dokploy settings. Determine whether the feature is enabled for any project or repository.
    Affected if The preview deployment feature is enabled.
  4. Inspect recent preview deployment logs
    Review the deployment logs or audit trails for preview environments. Look for deployment triggers that originated from pull requests on public repositories.
    Affected if There are recent preview deployments triggered by pull requests from public repositories.
  5. Audit exposed environment variables
    Examine any environment variables, secrets, or credentials that may have been transmitted to or rendered in preview deployment environments.
    Affected if Sensitive environment variables or secrets were present in preview deployment configurations.

You are affected if Dokploy version is below 0.24.3 and the preview deployment feature is enabled for any public repository, as unauthenticated attackers can exploit this to access secrets and execute code.

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
Upgrade available Upgrade to 0.24.3 or later
Fixed in 0.24.3
Vendor patch github.com →
Interim mitigation

Upgrade Dokploy to version 0.24.3 or later. Until patched, avoid connecting public repositories with the preview deployment feature enabled, as unauthenticated attackers can exploit this to access secrets and execute arbitrary code.

Recommended fix High confidence

0.24.3

  1. Backup your current Dokploy instance and all associated data
  2. Upgrade Dokploy to version 0.24.3 or later
  3. After upgrading, verify that preview deployments now require proper authentication
  4. Review existing preview deployments and rotate any exposed secrets or environment variables

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

Fix this in Dokploy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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