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 quest-bot |
|
| Vendors & Products |
Duck-organization
Duck-organization quest-bot |
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 | 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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-11T19:38:00.196Z
Reserved: 2026-05-18T21:25:34.497Z
Link: CVE-2026-47172
Updated: 2026-06-11T19:37:25.942Z
Status : Deferred
Published: 2026-06-11T19:16:45.240
Modified: 2026-06-11T20:58:18.123
Link: CVE-2026-47172
No data.
OpenCVE Enrichment
Updated: 2026-06-12T20:22:06Z