Security readout for executives and security teams
Plain-English summary
Dokploy versions 0.26.5 and earlier allow an authenticated user to write files outside intended paths during deployment. On remote server deployments, that can become full server compromise, including remote code execution, data theft, and persistence. The source does not show active exploitation, but the impact is severe.
Executive priority
Treat this as urgent for any Dokploy-backed production or shared environment. A low-privileged authenticated deployment user may be enough to compromise remote servers, so containment and vendor-guided remediation should happen quickly.
Technical view
The issue is a path traversal/arbitrary file write flaw during application deployment in Dokploy <=0.26.5. With the remote server deployment feature, arbitrary writes can reach remote server filesystems and bypass container isolation, enabling code execution through existing scheduled execution paths and broader compromise.
Likely exposure
Self-hosted Dokploy installations running 0.26.5 or earlier are potentially exposed. Risk is highest where authenticated users can deploy applications, and where Dokploy is configured to deploy to remote servers.
Exploitation context
The source states exploitation requires authenticated access and no user interaction. CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence is limited to the CVE bundle and Dokploy GitHub advisory reference. The bundle does not name a fixed release or concrete mitigation. Avoid assuming exploit availability; focus validation on version, authenticated deployment access, and remote server deployment usage.
Mitigation direction
- Check the Dokploy advisory for fixed versions or official mitigation guidance.
- Restrict Dokploy access to trusted authenticated users only.
- Disable or limit remote server deployments until vendor guidance is applied.
- Audit Dokploy deployments and remote hosts for unexpected file changes.
- Review scheduled tasks and persistence locations for unauthorized changes.
Validation and detection
- Inventory all Dokploy instances and record deployed versions.
- Flag any instance running Dokploy 0.26.5 or earlier.
- Confirm whether remote server deployment is enabled or used.
- Review deployment history for unexpected authenticated activity.
- Inspect affected remote servers for suspicious scheduled tasks or files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-35: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45661 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-66v7-g3fh-47h3CVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Path Traversal: '.../...//'
Path Traversal: '.../...//' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.