Skip to content
Cloud

CVE-2026-72882

CRITICAL
Critical
EPSS 0.36%Patch availableAug 11, 2026

Authenticated RCE in Dokploy via file mount path injection (web→SSH).

common questions

Is CVE-2026-72882 being exploited?

Not confirmed. CVE-2026-72882 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.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-72882?

CVE-2026-72882 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-72882?

Yes. A fix has been recorded for CVE-2026-72882. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72882 affect?

CVE-2026-72882 affects Dokploy <= 0.28.8, Dokploy web interface (file mounts), Configured remote managed servers accessed via SSH. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72882?

Upgrade Dokploy to a fixed release, restrict web/SSH access, and audit mounts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Dokploy <= 0.28.8Dokploy web interface (file mounts)Configured remote managed servers accessed via SSH
impact

Authenticated attacker can inject shell metacharacters in filePath to execute arbitrary commands on remote managed hosts via SSH (remote host RCE).

action required

Immediate action required

affected versions
Dokploy dokploy
  • affected<= 0.28.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free