Servers and applications
CVE-2026-129992
Failed builds and backups send every application secret in plain text to notifications
- Severity
- Medium 6.3
- Published
- 12 Nov 2026
- Last changed
- 19 Nov 2026
- Added to UpHeron
- 16 Nov 2026
- Fixed in
- 0.31.0, 0.31.1
- Exploit chance
- 0.3% in the next 30 daysHigher than 22% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Information exposure through sent data (CWE-201)CWE-214Sensitive information in log files (CWE-532)
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N- Also known as
- GHSA-w452-9gw6-323p
- Sources
- CVE Program, Project advisories (GitHub)
Description
When a Railpack build fails, Dokploy sends the full build command to every notification channel. That command holds every environment variable of the application as export NAME=value. So one failed build sends all application secrets in plain text to email, Slack, Discord, Telegram or a webhook.
Failed database backups do the same with the database password and the S3 destination keys. Dokploy also writes the same text to its own container log.
I saw this on v0.30.9 and read the same code in v0.30.10. I checked the Railpack builder and the database backups. I did not check the Nixpacks builder.
How the secrets get into the command:
- packages/server/src/utils/builders/railpack.ts: for each environment variable, the builder adds export NAME= to the bash command. It also passes each variable to railpack prepare as --env NAME=value.
- packages/server/src/utils/backups/utils.ts: getS3Credentials puts --s3-access-key-id and --s3-secret-access-key on the rclone command line.
Affected software
| Software | Affected versions |
|---|---|
DokployServers and applications · cna:dokploy|dokploy |
|
DokployServers and applications · github:dokploy/dokploy |
|
About Dokploy
Open Source Alternative to Vercel, Netlify and Heroku.
- Total downloads
- 6MDokploy
- Docker Hub pulls
- 16,318,110Docker Hub, 15 Nov 2026
- GitHub stars
- 38,516GitHub, 15 Nov 2026
- Forks
- 3,176GitHub, 15 Nov 2026
- Latest release
- v0.31.2GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- First published on GitHub
- 19 Apr 2024GitHub
Source code Website Docker image
Vulnerabilities in Dokploy
- In our list
- 139
- Published in the last 12 months
- 135
- Critical, last 12 months
- 62
- High, last 12 months
- 44
- Known exploited
- 0
- CVE-2026-133520Dokploy 0.28.0 before 0.31.1 Path Traversal via patch.readRepoDirectories repoPathMedium 5.3 20 Nov 2026
- CVE-2026-129989Dokploy: OS Command Injection via unsanitized publishDirectory in Nixpacks build pipelineCritical 9.9 18 Nov 2026
- CVE-2026-129987Dokploy: Authenticated RCE via Database Password Command SubstitutionCritical 9.9 18 Nov 2026
- CVE-2026-129433Dokploy before 0.31.1 OS Command Injection via Compose Backup serviceNameCritical 9.4 14 Nov 2026
- CVE-2026-128328Dokploy 0.28.0 before 0.31.1 Path Traversal via patch.readRepoDirectories repoPathMedium 5.3 13 Nov 2026
- CVE-2026-128329Dokploy 0.28.0 before 0.31.1 Path Traversal via patch.readRepoFileHigh 8.3 13 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-129992
- GitHub Advisory Database https://github.com/advisories/GHSA-w452-9gw6-323p
- github.com https://github.com/Dokploy/dokploy/security/advisories/GHSA-w452-9gw6-323p