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

> Unauthorized organization members can retrieve plaintext Git provider credentials and secrets via unprotected API endpoints, enabling access to private repositories.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-wx75-vxph-2m2f

## What is CVE-2026-86059?

CVE-2026-86059 is a critical missing authorization vulnerability in dokploy, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-86059?


## How do I fix CVE-2026-86059?

No fix has been published for CVE-2026-86059 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86059 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86059 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86059 and fix it if it is affected.

What it is: CVE-2026-86059 is a critical missing authorization vulnerability in dokploy, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86059 exists.

Affected product: dokploy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86059/ (Markdown: https://insights.sbomify.com/CVE-2026-86059/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86059
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86059
- OSV: https://osv.dev/vulnerability/CVE-2026-86059

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86059/
Summaries are generated and may contain mistakes; the official description above is the record.