Servers and applications
GHSA-v549-87g2-g95q
Credential-redaction fix leaves Docker-source passwords in application responses
- Severity
- High 8.3
- Published
- 12 Nov 2026
- Last changed
- 12 Nov 2026
- Added to UpHeron
- 12 Nov 2026
- Fixed in
- 0.31.1
- Weakness
- Information exposure (CWE-200)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
A base member may read an assigned application's configuration. That access should not reveal the plaintext password used to pull from its private Docker registry.
Commit c968a275 removed passwords from the registry, buildRegistry, and rollbackRegistry relations returned to service readers. Applications using a direct Docker image store equivalent private-registry credentials in the application row itself.
findApplicationById() still selects the top-level username, password, and registryUrl columns. application.one returns that object unchanged to any base member with read access to the service, although that role has no registry permission.
application.saveDockerProvider stores the Docker registry username and password directly on the application row. These fields are separate from the optional registry, buildRegistry, and rollbackRegistry relations.
Affected software
| Software | Affected versions |
|---|---|
DokployServers and applications · github:dokploy/dokploy |
|
References
- GitHub Advisory Database https://github.com/advisories/GHSA-v549-87g2-g95q
- github.com https://github.com/Dokploy/dokploy/security/advisories/GHSA-v549-87g2-g95q