CVE
Dokploy remote code exposure of secrets in build and backup alerts
- Exploited
- No known exploitation
- Fix
- Fixed in 0.31.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.31.0.
Summary
Dokploy, a self-hosted platform-as-a-service, exposes application environment variables, database passwords, and S3 access keys in plain text when failed builds and database backups send error messages to notifications and persistent logs. An attacker who has a low-privilege account on the network can reach this without user action, but only when the App Build Error or Database Backup notification setting is enabled.
Original description
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.0, failed Railpack builds and database backups propagate an execution error containing the full command, exposing application environment variables, database passwords, and S3 access keys embedded in those commands. When the corresponding App Build Error or Database Backup notification setting is enabled, the disclosure can send secrets to email, Slack, Discord, Telegram, or webhooks; the same secrets are written separately to persistent Dokploy container logs, which may be accessible to more principals than the affected service. This issue is fixed in version 0.31.0.
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.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.31.0.
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-129992 (Dokploy: Failed builds and backups send every application secret in plain text to notifications), 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-129992 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: fixed in 0.31.0
Fixed versions: 0.31.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129992 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129992 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-w452-9gw6-323p
- https://github.com/Dokploy/dokploy/pull/5733
- https://github.com/Dokploy/dokploy/commit/e76283bc0969f8d77563e22073c66c36c88e7b93
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.0
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-129992
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-129992"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dokploy dokploy
fixed in 0.31.0
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Dokploy/dokploy · Advisory GHSA-w452-9gw6-323p |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129992 |
| Record | NVD · CVE-2026-129992 |
| Other links 3 | |
| Repository | GitHub · Dokploy/dokploy · Pull request #5733 |
| Repository | GitHub · Dokploy/dokploy · Commit e76283bc |
| Repository | GitHub · Dokploy/dokploy · Release v0.31.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129992
Is CVE-2026-129992 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-129992?
dokploy: before 0.31.0.Source: cve.now feed data
How do I fix CVE-2026-129992?
Upgrade to a fixed version: 0.31.0.Source: cve.now feed data