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.
Published: 2026-06-11
Score: 9.5 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an attacker to push a pull request that is then captured by a privileged GitHub Actions workflow, which builds and deploys that code into a Docker image and runs it in production. This results in the bot running arbitrary code with full privileges, effectively giving the attacker control over the bot’s runtime environment. The weakness is a security misconfiguration that permits untrusted code to enter a privileged deployment pipeline.

Affected Systems

The issue affects the Duck Organization’s Quest Bot for Discord, specifically versions prior to 1.0.3. The repository’s privileged deploy workflow, which runs after the unprivileged build workflow, is the root cause of the vulnerability.

Risk and Exploitability

The CVSS score of 9.5 indicates critical severity, reflecting high confidentiality, integrity, and availability impact. While no EPSS score is published, the absence of a known exploit in the KEV catalog does not diminish the likelihood of exploitation in environments that enable the described workflow. Attackers must be able to submit a pull request targeting the main branch; the workflow’s condition inadvertently treats this as a deployable event, allowing the attacker to execute code in a privileged context. The attack can be performed via the normal PR submission interface without additional credentials beyond those required to open a PR.

Generated by OpenCVE AI on June 11, 2026 at 22:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Quest Bot to version 1.0.3 or later to remove the privileged deployment workflow.
  • Configure the repository’s GitHub Actions settings to restrict the deploy workflow to a specific, trusted branch or to manual approval only.
  • Disable or modify the ‘build’ action to reject commits that originate from untrusted pull requests, ensuring only verified code can trigger Docker builds.

Generated by OpenCVE AI on June 11, 2026 at 22:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 11 Jun 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 11 Jun 2026 19:00:00 +0000

Type Values Removed Values Added
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.
Title Quest Bot: Untrusted pull request code can be built and deployed by privileged `workflow_run` deployment.
Weaknesses CWE-829
References
Metrics cvssV4_0

{'score': 9.5, 'vector': '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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-06-11T19:38:00.196Z

Reserved: 2026-05-18T21:25:34.497Z

Link: CVE-2026-47172

cve-icon Vulnrichment

Updated: 2026-06-11T19:37:25.942Z

cve-icon NVD

Status : Deferred

Published: 2026-06-11T19:16:45.240

Modified: 2026-06-11T20:58:18.123

Link: CVE-2026-47172

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-11T22:30:09Z

Weaknesses
  • CWE-829

    Inclusion of Functionality from Untrusted Control Sphere