Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 12 Jun 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Duck-organization
Duck-organization duck-site |
|
| Vendors & Products |
Duck-organization
Duck-organization duck-site |
Thu, 11 Jun 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 11 Jun 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Duck Site: Untrusted pull request code can trigger privileged production deployment | |
| Weaknesses | CWE-829 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-11T19:47:33.704Z
Reserved: 2026-05-18T21:25:34.497Z
Link: CVE-2026-47174
Updated: 2026-06-11T19:41:21.455Z
Status : Deferred
Published: 2026-06-11T19:16:45.557
Modified: 2026-06-11T21:16:22.033
Link: CVE-2026-47174
No data.
OpenCVE Enrichment
Updated: 2026-06-12T20:21:44Z