Security readout for executives and security teams
Plain-English summary
Dokploy’s registry deletion path can let a logged-in attacker make the server run unintended shell commands. Because Dokploy manages application deployment infrastructure, successful abuse could expose secrets, alter hosted services, or disrupt availability on affected self-hosted instances.
Executive priority
Treat as high priority for any Dokploy-backed production environment. The risk is not confirmed as actively exploited, but the impact reaches the deployment host and services it manages.
Technical view
In Dokploy 0.29.0 and earlier, deleteRegistry in packages/server/src/services/registry.ts runs docker logout with an unescaped registryUrl. The same file escapes docker login, showing the logout path is inconsistent. The flaw is CWE-78 command injection with CVSS 8.8, requiring low privileges and no user interaction.
Likely exposure
Exposure is likely limited to self-hosted Dokploy installations running version 0.29.0 or earlier where authenticated users can create, manage, or delete registries.
Exploitation context
The source bundle does not show known active exploitation, and the CVE is not listed as KEV. Exploitation requires authenticated access, but CVSS indicates low attack complexity and high confidentiality, integrity, and availability impact.
Researcher notes
Evidence is strongest for the vulnerable code path and affected versions. The bundle does not name a fixed release, workaround, proof of exploitation, or KEV listing, so remediation should track Dokploy’s official advisory.
Mitigation direction
- Check Dokploy vendor advisory and releases for the named fixed version or workaround.
- Upgrade affected Dokploy instances when vendor guidance identifies a safe release.
- Limit registry management permissions to trusted administrators only.
- Review existing registryUrl values for unexpected shell metacharacters or suspicious content.
- Restrict network and host privileges for the Dokploy service where feasible.
Validation and detection
- Inventory Dokploy instances and identify versions at or below 0.29.0.
- Confirm whether non-admin or low-privileged users can manage registries.
- Review registry deletion audit logs around suspicious registryUrl values.
- Inspect deployments for package/server/src/services/registry.ts behavior if running custom builds.
- Check CVE and GitHub advisory updates for patch status changes.
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-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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 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-45662 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:U/C:H/I:H/A:H2.85.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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-827c-7x62-29jqCVE 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 Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.