PT-2026-48713 · Duck Organization · Duck-Site

Published 2026-06-11 · Updated 2026-06-11 · CVE-2026-47174

NVD

CVSS v4.0

9.5

Critical

Base vector

AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In Duck Site before version 1.0.1, the repository has a deploy workflow that runs after the build workflow completes. The build workflow runs on pull requests, while the deploy workflow runs with package-write permissions and deployment secrets. If an attacker can make a pull request build satisfy the deploy workflow’s main branch condition, the deploy job checks out the triggering workflow commit, builds it into a Docker image, pushes it as latest, and triggers Dokploy deployment. This can allow attacker-controlled pull request code to become the deployed production site image without being merged. This issue has been patched in version 1.0.1.

Exploit

Fix

Weakness Enumeration

CWE-829

Related Identifiers

CVE-2026-47174

Affected Products

Duck-Site

References · 2

• 🔥 https://github.com/duck-organization/duck-site/security/advisories/GHSA-qj93-7xrg-rvhw · Exploit
• https://nvd.nist.gov/vuln/detail/CVE-2026-47174 · Security Note