CVE-2026-86059: Dokploy: Git Provider Credential Exposure via Unprotected .one Endpoints and application.one

Published Sep 22, 2026
·
Updated

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy organization members without Git provider access can retrieve plaintext provider credentials through github.one, gitlab.one, gitea.one, and bitbucket.one because those protected procedures return full provider rows without applying getAccessibleGitProviderIds or an organization check. The application.one route also returns nested GitHub, GitLab, Gitea, and Bitbucket relations from findApplicationById with GitHub App private keys, OAuth tokens, client secrets, webhook secrets, and app passwords even when hasGitProviderAccess is false. A member with application read access or a provider identifier can therefore bypass per-member provider assignment and use the exposed credentials to access private repositories or manipulate external workflows. This issue is fixed in version 0.29.13.

Affected Software

1 affected component
Dokploy Dokploy<0.29.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Dokploy to a version that resolves this vulnerability.

    Fixed in 0.29.13

Event History

Sep 22, 2026
CVE Published
via MITRE·04:11 PM
Data Sourced
via MITRE·04:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which Dokploy deployments are affected?

Dokploy versions before 0.29.13 are affected. Organizations are exposed when members have application read access or can supply a Git provider identifier, even if those members were not assigned access to the Git provider.

2

What level of access does an attacker need?

An attacker must already be an organization member with application read access, or have a provider identifier for the provider endpoints. No user interaction is required, and the attacker does not need Git provider access assigned by the organization.

3

What credentials could be exposed?

The affected routes can disclose plaintext Git provider credentials, including GitHub App private keys, OAuth tokens, client secrets, webhook secrets, and app passwords. These credentials may allow access to private repositories or manipulation of external workflows.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203