CVE
Dokploy missing authorization in Docker network endpoints
Affects self-hosted Dokploy installs where Member accounts with no Docker permissions can reach the network endpoints; tested on v0.30.6. Fixed in 0.31.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.31.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Self-hosted Dokploy install (tested on v0.30.6) Member account with no Docker permissions
Summary
Dokploy, a self-hostable Platform as a Service, has missing authorization checks on its Docker network functions, so any regular member with a login can list, create, import, or delete Docker networks, including on servers they should not control. The flaw can be reached remotely by a user with low-privilege credentials, and it can disrupt service connectivity or change network configuration.
Original description
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, every network.* procedure is only authentication-protected and does not require the Docker permission, allowing a standard member to list, inspect, create, import, recreate, resynchronize, and delete Docker networks. A member can disrupt service connectivity or alter network configuration, and create/import operations can target an unchecked serverId. This issue is fixed in version 0.31.1.
Who should check
Teams running self-hosted Dokploy before 0.31.1, especially those with member accounts in shared organizations
“Missing authorization on all network.* endpoints”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Self-hosted Dokploy install (tested on v0.30.6) Member account with no Docker permissionsUpgrade to a fixed version: 0.31.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129990 (Dokploy: Missing authorization on all network. endpoints (Member -> create/delete docker networks on org servers, cross-org access via…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129990 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: fixed in 0.31.1
Fixed versions: 0.31.1.
Conditions (all must be true for the bug to be hit):
- Self-hosted Dokploy install (tested on v0.30.6) (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-r6pv-8cgq-pvxv)
- Member account with no Docker permissions (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-r6pv-8cgq-pvxv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129990 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129990 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-r6pv-8cgq-pvxv
- https://github.com/Dokploy/dokploy/pull/5967
- https://github.com/Dokploy/dokploy/commit/b4cc3db217a02c5cf58b906a7f3508f4b576d670
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129990
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129990"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dokploy dokploy
fixed in 0.31.1
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Dokploy/dokploy · Advisory GHSA-r6pv-8cgq-pvxv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129990 |
| Record | NVD · CVE-2026-129990 |
| Other links 3 | |
| Repository | GitHub · Dokploy/dokploy · Pull request #5967 |
| Repository | GitHub · Dokploy/dokploy · Commit b4cc3db2 |
| Repository | GitHub · Dokploy/dokploy · Release v0.31.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129990
Is CVE-2026-129990 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A Member account with no Docker permissions can delete dokploy-network or any service network, which cuts connectivity for every app on that network. It can also create networks with attacker-chosen driver and IPAM options.Source: github.com
Which versions are affected by CVE-2026-129990?
dokploy: before 0.31.1.Source: cve.now feed data
Am I affected, and how do I check?
The bug was tested on a self-hosted Dokploy install at v0.30.6 and involves Member accounts that have no Docker permissions. To check, compare the installed Dokploy version with 0.31.1 and review the permissions assigned to Member accounts.Source: github.com
How do I fix CVE-2026-129990?
Upgrade Dokploy to 0.31.1 or later, which is the listed fixed version. The facts do not name vendor patch ids.Source: github.com