Is CVE-2026-47174 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47174 being exploited in the wild.

How severe is CVE-2026-47174?

Informational severity, with a CVSS score of 9.5, published 11 June 2026.

Which products and versions are affected?

Duck-Organization Duck Site < 1.0.1.

Is there a fix for CVE-2026-47174?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-47174 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-47174?

Check whether you run Duck-Organization Duck Site at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47174: Duck Site untrusted code deployment via GitHub Actions workflow

Q: Is there a fix for CVE-2026-47174?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-47174 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-47174?

Check whether you run Duck-Organization Duck Site at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47174 · Severity: info · CVSS 9.5 · Published 2026-06-11

A security flaw in the automated deployment process of Duck Site allows unauthorized individuals to push malicious code directly to the live production website. By submitting a specially crafted pull request, an attacker can bypass the normal review and merge process, tricking the system into building and deploying their unapproved changes. This could lead to website defacement, the theft of user credentials, or the distribution of malicious software to site visitors.

Vendors: Duck-Organization.

Quick answers

Is CVE-2026-47174 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47174 being exploited in the wild.
How severe is CVE-2026-47174?: Informational severity, with a CVSS score of 9.5, published 11 June 2026.
Which products and versions are affected?: Duck-Organization Duck Site < 1.0.1.
Is there a fix for CVE-2026-47174?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47174 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-47174?: Check whether you run Duck-Organization Duck Site at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the GitHub Actions CI/CD pipeline where a privileged 'deploy' workflow is triggered by the completion of a 'build' workflow. The deploy workflow incorrectly uses the commit SHA from the triggering pull request rather than the trusted main branch. If an attacker names their source branch 'main' in a fork and submits a pull request, the deployment logic's branch condition is satisfied. This allows the attacker's code to be built into a Docker image, pushed to the GitHub Container Registry (GHCR) as 'latest', and deployed via Dokploy without any manual approval or code merge. This is a supply-chain compromise resulting from the inclusion of functionality from an untrusted control sphere (CWE-829).

Affected products

duck-organization Duck Site < 1.0.1

Timeline

2026-05-17: advisory: GitHub Security Advisory published by maintainers
2026-06-11: disclosed: CVE published to NVD

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.