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.
CVSS

No CVSS.

Configurations

No configuration.

History

11 Jun 2026, 21:16

Type Values Removed Values Added
References () https://github.com/duck-organization/duck-site/security/advisories/GHSA-qj93-7xrg-rvhw - () https://github.com/duck-organization/duck-site/security/advisories/GHSA-qj93-7xrg-rvhw -

11 Jun 2026, 19:16

Type Values Removed Values Added
New CVE

Information

Published : 2026-06-11 19:16

Updated : 2026-06-17 10:54


NVD link : CVE-2026-47174

Mitre link : CVE-2026-47174

CVE.ORG link : CVE-2026-47174


JSON object : View

Products Affected

No product.

CWE
CWE-829

Inclusion of Functionality from Untrusted Control Sphere