GPU VulnDB

Database/Container, Kubernetes & orchestration

Dokploy: network procedures skip the Docker permission check, so any member can rewire or delete Docker networks

CVSS 8.3CVE-2026-129990Container, Kubernetes & orchestrationcurated

Impact

In Dokploy before 0.31.1, the network.* procedures only check that the caller is logged in, not that they hold the Docker permission. Any standard member can list, inspect, create, import, recreate, resync and delete Docker networks. That lets them cut service connectivity or change how workloads are attached across the hosts Dokploy manages. Create and import also accept a serverId that is not checked, so a member can act on servers outside their scope. On a shared Dokploy install this turns a low-privilege account into the power to cause outages across the platform.

Who can reach it

Any authenticated Dokploy member, including members without the Docker permission, who can reach the Dokploy web/API endpoint.

What to do

Upgrade Dokploy to 0.31.1 and restart the Dokploy service. Running containers keep running during the upgrade, but the panel and API are briefly unavailable. Until then, cut member accounts to trusted users and check Docker network configuration for changes you did not make.

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.