CVE-2026-72733
Authenticated command injection in Dokploy backup restore allows host RCE.
Is CVE-2026-72733 being exploited?
Not confirmed. CVE-2026-72733 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.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-72733?
CVE-2026-72733 is rated Critical with a CVSS score of 9.9. 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-72733?
Yes. A fix has been recorded for CVE-2026-72733. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72733 affect?
CVE-2026-72733 affects Dokploy < 0.29.13 (self-hosted PaaS). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72733?
Upgrade to Dokploy >=0.29.13; restrict backup-restore rights; audit host logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker with backup-restore permission can inject OS commands, achieving remote code execution on the Dokploy host.
Immediate action required
- affected< 0.29.13
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.