Servers and applications
GHSA-wf8r-8h5f-pxqm
Notification parent/child ID confusion allows cross-tenant alert and credential hijacking
- Severity
- High 7.6
- Published
- 12 Nov 2026
- Last changed
- 12 Nov 2026
- Added to UpHeron
- 12 Nov 2026
- Fixed in
- 0.31.1
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
An organization administrator may update that organization's notification providers. Authorizing one parent notification must not permit changes to an independently supplied child provider owned by another tenant.
Every notification update accepts two independent global IDs, a parent notificationId and a provider-specific child ID such as slackId, gotifyId, or teamsId. The router authorizes only the parent. The service then updates the separately supplied child without verifying that it belongs to the authorized notification or organization.
An attacker can create an attacker-owned notification, pass its authorized parent ID together with another tenant's child ID, and replace the victim webhook, server URL, token, email credentials, or API key. Future deployment, build-error, backup, restart, cleanup, and server-threshold alerts can be redirected to the attacker or suppressed.
Affected software
| Software | Affected versions |
|---|---|
DokployServers and applications · github:dokploy/dokploy |
|
References
- GitHub Advisory Database https://github.com/advisories/GHSA-wf8r-8h5f-pxqm
- github.com https://github.com/Dokploy/dokploy/security/advisories/GHSA-wf8r-8h5f-pxqm