Dokploy CVE-2026-129433: Critical Authenticated RCE

Résumé

Pixel shares a security alert about CVE-2026-129433, a critical authenticated remote code execution vulnerability in Dokploy with a CVSS score of 9.9. The announcement explains the risk to Docker hosts, containers, and secrets, and urges users to upgrade, audit organization members, secure hosts, and rotate exposed secrets.

DEV Community

CVE-2026-129433: Dokploy 9.9 — The Access Control Is the Member List

CVE-2026-129433 is a CVSS 9.9 authenticated RCE in Dokploy, the self-hosted Docker deployment platform. Vector: AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H The PR:L requires an account. The S:C scope change crosses from the web app to the Docker host. The result is root on the host — every container, every env var, every secret the team deployed. Why PR:L is thin on a team platform: Dokploy's access model is an org member list. The precondition is the product's normal usage. What to do: Upgrade to the fixed release (confirm versions from the Dokploy advisory) Audit the org member list — remove stale accounts, shared logins; enable MFA Treat the Docker host as tier zero — segment it, monitor it If exposed on a vulnerable version: rotate all secrets reachable from the host The access control for this CVE is the member list. The audit is part of the fix the patch doesn't perform. Full write-up: https://threataft.com/articles/cve-2026-129433-dokploy-authenticated-rce-docker
Dokploy CVE-2026-129433: Critical Authenticated RCE
Powered by Readybot.io

Les dernières actus de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …