GPU VulnDB

Database/Container, Kubernetes & orchestration

Dokploy: unquoted dockerImage field gives command execution on the build host

CVSS 9.6CVE-2026-72877Container, Kubernetes & orchestrationcurated

Impact

The dockerImage field of an application is validated only as an optional string and then interpolated unquoted into a shell command in buildRemoteDocker(), so shell command substitution in that field runs as the build process on the local build host or on the remote SSH build target. Any member who can create or update an application - a routine permission on a shared instance - reaches it. The build host is where registry credentials, deploy keys and every other project's source live, so this is a straight path from ordinary application permissions to the secrets of unrelated projects. Distinct from the volume-backup and registry-credential injections fixed in the same release: different field, different code path, different commit.

Who can reach it

Network access to the Dokploy API with an authenticated account holding application create or update permission. Triggered when the application is built, on whichever host does the build.

What to do

Upgrade to Dokploy 0.29.13 and restart the Dokploy stack (fix in commit cba0b25). No mitigation short of the upgrade is published; restricting who holds application create/update permission reduces the pool of callers but does not close the path. The restart interrupts in-flight builds and deploys. Treat registry credentials and deploy keys reachable from the build host as potentially exposed on a shared instance.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.