CVE
Dokploy unauthorized read of SSH private key via settings API
- Exploited
- No known exploitation
- Fix
- Fixed in 0.31.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.31.1.
Summary
Dokploy, a self-hosted platform-as-a-service tool, has a flaw that lets any logged-in member, not just administrators, read the stored web-server SSH private key through the settings.getWebServerSettings function. An attacker with a basic member account can do this remotely over the network, which could expose credentials that only administrators are meant to manage.
Original description
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the settings.getWebServerSettings protected procedure returns the complete global web-server settings object to any authenticated member, including the stored sshPrivateKey, even though settings.saveSSHPrivateKey requires an administrator. A default member can therefore retrieve infrastructure, deployment, or server-management credentials that only an administrator can configure. This issue is fixed in version 0.31.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.31.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129993 (Dokploy member users can read the global web-server SSH private key through settings.getWebServerSettings), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129993 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: fixed in 0.31.1
Fixed versions: 0.31.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129993 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129993 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-fr95-6x4c-3c5g
- https://github.com/Dokploy/dokploy/pull/5913
- https://github.com/Dokploy/dokploy/commit/e9910d76f0dbfdded052f5c2320045ca707a1e08
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129993
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129993"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dokploy dokploy
fixed in 0.31.1
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Dokploy/dokploy · Advisory GHSA-fr95-6x4c-3c5g |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129993 |
| Record | NVD · CVE-2026-129993 |
| Other links 3 | |
| Repository | GitHub · Dokploy/dokploy · Pull request #5913 |
| Repository | GitHub · Dokploy/dokploy · Commit e9910d76 |
| Repository | GitHub · Dokploy/dokploy · Release v0.31.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129993
Is CVE-2026-129993 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-129993?
dokploy: before 0.31.1.Source: cve.now feed data
How do I fix CVE-2026-129993?
Upgrade to a fixed version: 0.31.1.Source: cve.now feed data