CVE-2026-72737
Auth bypass in Dokploy allows cross-tenant S3 credential exposure and backup tampering
Is CVE-2026-72737 being exploited?
Not confirmed. CVE-2026-72737 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-72737?
CVE-2026-72737 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72737?
Yes. A fix has been recorded for CVE-2026-72737. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72737 affect?
CVE-2026-72737 affects Dokploy <= 0.29.8, apps/dokploy/server/api/routers/backup.ts, packages/server/src/utils/backups/utils.ts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72737?
Restrict backup perms, rotate S3 keys, audit backups, and upgrade when a patch is released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user with backup perms can obtain another org's S3 keys, read/modify backups, or poison backups across tenants.
Immediate action required
- affected<= 0.29.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.