CVE-2026-47174

Source
https://cve.org/CVERecord?id=CVE-2026-47174
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47174.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-47174
Aliases
  • GHSA-qj93-7xrg-rvhw
Published
2026-06-11T18:46:59.572Z
Modified
2026-07-08T08:13:50.058892984Z
Severity
  • 9.5 (Critical) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CVSS Calculator
Summary
Duck Site: Untrusted pull request code can trigger privileged production deployment
Details

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.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/47xxx/CVE-2026-47174.json",
    "cwe_ids": [
        "CWE-829"
    ],
    "cna_assigner": "GitHub_M"
}
References

Affected packages

Git / github.com/duck-organization/duck-site

Affected ranges

Type
GIT
Repo
https://github.com/duck-organization/duck-site
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
Database specific
{
    "source": [
        "AFFECTED_FIELD",
        "DESCRIPTION"
    ],
    "extracted_events": [
        {
            "introduced": "0"
        },
        {
            "fixed": "1.0.1"
        }
    ]
}

Affected versions

v1.*
v1.0.0

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47174.json"