Skip to content
Fencer Intel
medium 6.3

CVE-2026-129992 json

Dokploy: Failed builds and backups send every application secret in plain text to notifications

published 7d ago modified 2h ago also EUVD-2026-129329 , GHSA-w452-9gw6-323p

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository Dokploy/dokploy. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

Is CVE-2026-129992 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2h ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-19).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected products

  • Dokploy dokploy

Classification

Weakness
  • CWE-201 Insertion of Sensitive Information Into Sent Data
  • CWE-214 Invocation of Process Using Visible Sensitive Information
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of Dokploy/dokploy published their own advisory on GitHub. Reviewed sources take precedence over it.