Duck Site: Untrusted pull request code can trigger privileged production deployment
CVE-2026-47174

9.5CRITICAL

Key Information:

Vendor

Duck-organization

Status
Duck-site
Vendor
CVE Published:
11 June 2026

What is CVE-2026-47174?

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.

Affected Version(s)

duck-site < 1.0.1

References

https://github.com/duck-organization/duck-site/security/a...
x_refsource_CONFIRM

CVSS V4

Score:
9.5
Severity:
CRITICAL
Confidentiality:
High
Integrity:
High
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Attack Required:
Physical
Privileges Required:
Undefined
User Interaction:
None

Timeline

  • Vulnerability published

  • Vulnerability Reserved

.