CVE-2026-86059
Deferred Deferred - Pending Action

Exposed Git Provider Credentials in Dokploy

Publication date: 2026-09-22

Last updated on: 2026-09-22

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-22
Last Modified
2026-09-22
Generated
2026-09-22
AI Q&A
2026-09-22
EPSS Evaluated
N/A
NVD
CVE-2026-86059
EUVD
EUVD-2026-84544

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
dokploy dokploy From 0.29.8 (inc)
dokploy dokploy 0.29.13
dokploy dokploy to 0.29.13 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Dokploy is a self-hostable Platform as a Service (PaaS). A vulnerability in versions before 0.29.13 allows organization members without Git provider access to retrieve plaintext credentials for GitHub, GitLab, Gitea, and Bitbucket through specific routes. This happens because protected procedures return full provider rows without proper access checks or organization validation.

Detection Guidance

To detect this vulnerability, check if your Dokploy instance is running a version prior to 0.29.13. Inspect network traffic for requests to endpoints like github.one, gitlab.one, gitea.one, bitbucket.one, or application.one. Verify if these endpoints return sensitive Git provider credentials in plaintext without proper authorization checks.

Impact Analysis

An attacker with application read access or provider identifier can bypass access controls and retrieve exposed credentials. This allows them to access private repositories or manipulate external workflows, potentially leading to data breaches or unauthorized code changes.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, including OAuth tokens, private keys, and API tokens, which may violate GDPR's data protection requirements for confidentiality and integrity. For HIPAA, exposure of credentials could enable unauthorized access to protected health information if repositories contain such data.

Mitigation Strategies

Immediately upgrade Dokploy to version 0.29.13 or later to patch the vulnerability. Review organization member permissions to ensure only authorized users have access to Git providers. Audit exposed credentials and revoke any potentially compromised tokens or secrets.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86059. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart