CVE-2026-47172: CWE-829: Inclusion of Functionality from Untrusted Control Sphere in duck-organization quest-bot
Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.3, the repository has a privileged deploy workflow that runs after the unprivileged build workflow completes. The build workflow runs on pull requests, and the deploy workflow checks out the triggering workflow’s head_sha, builds that code into a Docker image, pushes it as latest, and triggers production deployment. If an attacker can open a pull request from a branch named main, the deploy workflow condition can treat the PR build as deployable and build the attacker-controlled commit in a privileged deployment context. This can result in malicious container deployment and production bot compromise. This issue has been patched in version 1.0.3.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-47172) in duck-organization's quest-bot involves the inclusion of functionality from an untrusted control sphere (CWE-829). The bot's deployment process includes a privileged deploy workflow that runs after an unprivileged build workflow triggered by pull requests. If an attacker opens a pull request from a branch named 'main', the deploy workflow mistakenly treats the PR build as deployable, building and deploying attacker-controlled code in a privileged context. This can lead to malicious container deployment and compromise of the production bot. The vulnerability is patched in version 1.0.3.
Potential Impact
An attacker who can open a pull request from a branch named 'main' can cause the deployment of malicious code in a privileged context, leading to full compromise of the production bot environment. This can result in unauthorized code execution and control over the bot's operations.
Mitigation Recommendations
Upgrade quest-bot to version 1.0.3 or later, where this vulnerability is patched. No other mitigation is required as the issue is resolved in the fixed version.
CVE-2026-47172: CWE-829: Inclusion of Functionality from Untrusted Control Sphere in duck-organization quest-bot
Description
Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.3, the repository has a privileged deploy workflow that runs after the unprivileged build workflow completes. The build workflow runs on pull requests, and the deploy workflow checks out the triggering workflow’s head_sha, builds that code into a Docker image, pushes it as latest, and triggers production deployment. If an attacker can open a pull request from a branch named main, the deploy workflow condition can treat the PR build as deployable and build the attacker-controlled commit in a privileged deployment context. This can result in malicious container deployment and production bot compromise. This issue has been patched in version 1.0.3.
CVSS v4.0
Score 9.5critical
Affected software
pkg:github/duck-organization/questbotRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-47172) in duck-organization's quest-bot involves the inclusion of functionality from an untrusted control sphere (CWE-829). The bot's deployment process includes a privileged deploy workflow that runs after an unprivileged build workflow triggered by pull requests. If an attacker opens a pull request from a branch named 'main', the deploy workflow mistakenly treats the PR build as deployable, building and deploying attacker-controlled code in a privileged context. This can lead to malicious container deployment and compromise of the production bot. The vulnerability is patched in version 1.0.3.
Potential Impact
An attacker who can open a pull request from a branch named 'main' can cause the deployment of malicious code in a privileged context, leading to full compromise of the production bot environment. This can result in unauthorized code execution and control over the bot's operations.
Mitigation Recommendations
Upgrade quest-bot to version 1.0.3 or later, where this vulnerability is patched. No other mitigation is required as the issue is resolved in the fixed version.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T21:25:34.497Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2b05d1815e7002b81ea666
Added to database: 6/11/2026, 7:00:33 PM
Last enriched: 6/11/2026, 7:15:17 PM
Last updated: 6/11/2026, 9:31:11 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.