Quick answers
- Is CVE-2026-47172 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47172 being exploited in the wild.
- How severe is CVE-2026-47172?
- Informational severity, with a CVSS score of 10, published 11 June 2026.
- Which products and versions are affected?
- Duck-Organization Quest Bot <= 1.0.2.
- Is there a fix for CVE-2026-47172?
- A patch was published on 2026-05-17: Version 1.0.3 released to address the vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47172 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-47172?
- Check whether you run Duck-Organization Quest Bot 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 interaction between the unprivileged 'build' workflow and the privileged 'deploy' workflow (using the workflow_run trigger). The deploy workflow incorrectly validates the source of a build by only checking if the branch name is 'main'. An attacker can fork the repository, create a branch named 'main', and submit a pull request. Because the deploy workflow checks out the 'head_sha' of the triggering workflow rather than a trusted reference, it builds and deploys the attacker's code to production. This grants the attacker access to production secrets, including Discord tokens and database credentials. The issue is fixed in version 1.0.3 by improving workflow validation.
Affected products
- duck-organization Quest Bot <= 1.0.2
Timeline
- 2026-05-17: patched: Version 1.0.3 released to address the vulnerability.
- 2026-06-11: disclosed: CVE-2026-47172 published.