Skip to main content
VulnerabilityPublished

CVE-2026-129992: dokploy · Insertion of Sensitive Information Into Sent Data

Affects dokploySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.31.0 when convenient.

Data as of 18 Nov 2026, 22:51 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.3
Patch
Available – fixed in 0.31.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade dokploy and dokploy/dokploy to 0.31.0.

Affected software

ProductAffectedFixed in
DokploydokployAffected
  • <0.31.0
Fixed in
  • 0.31.0
GitHubdokploy/dokploypkg:github/dokploy/dokployOther threatsAffected
  • <0.31.0
Fixed in
  • 0.31.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Dokploy to version 0.31.0 or later, where this vulnerability is fixed. Since this is a cloud-hosted service, the vendor manages remediation for the cloud environment. Users should verify that notification settings for App Build Error and Database Backup are configured appropriately to minimize exposure. Review and restrict access to persistent container logs to prevent unauthorized access to leaked secrets.

Description

Dokploy versions prior to 0.31.0 contain a vulnerability where failed Railpack builds and database backups expose sensitive information such as environment variables, database passwords, and S3 access keys. This occurs because execution errors propagate the full command containing these secrets. When notifications for App Build Error or Database Backup are enabled, these secrets can be sent to external services like email, Slack, Discord, Telegram, or webhooks. Additionally, the secrets are logged in persistent container logs, potentially accessible to unauthorized parties. This issue is fixed in version 0.31.0.

References

Community reviews

Loading reviews…