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.

Score

CVSS 4.0 9.5 Critical

Status

Deferred - security-advisories@github.com

Published

2026-06-11

Last modified

2026-10-26

Weaknesses

CWE-829

Affected products

• Duck-site (Duck-organization)

References

• https://github.com/duck-organization/duck-site/security/advisories/GHSA-qj93-7xrg-rvhw