CVE-2026-47172: Quest Bot: Untrusted pull request code can be built and deployed by privileged `workflow_run` deployment.
Noroxi assessment
Priority: Monitor (action score 38/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: duck-organization quest-bot 1.0.3.
Low priority for now. Upgrade to duck-organization quest-bot 1.0.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Jun 11, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-829
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 38 / 40 · 9.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 9.5
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
duck-organization quest-bot
- < 1.0.3affected
Same product
duck-organization: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-47171Quest Bot: Reminder messages allow stored mass mentions through `@everyone` and `@here`35Monitor
- CVE-2026-47189Quest Bot: AutoMod removal can delete rules from another guild by global rule ID33Monitor
- CVE-2026-47169Quest Bot: Manage Server users can configure AutoRole to grant Administrator to controlled joining accounts30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-47163Jun 11, 2026 · Quest Bot: Unprivileged users can create and remove AutoMod rules.28Monitor
- Later →CVE-2026-47173Jun 11, 2026 · Quest Bot: Ticket reason allows mass-mention injection25Monitor
- Later →CVE-2026-47175Jun 11, 2026 · Quest Bot: Moderation reason fields allow bot-powered `@everyone` / `@here` pings9Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| duck-organization quest-bot | 1.0.3 · description | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-07 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+87 d
- TodayNov 7, 2026+149 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-829 · Inclusion of Functionality from Untrusted Control SphereCVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Code InclusionCAPEC-175likelihood: Medium · Very High
- Serialized Data External LinkingCAPEC-201likelihood: High · High
- DTD InjectionCAPEC-228Medium
- Local Code InclusionCAPEC-251Medium
- PHP Local File InclusionCAPEC-252Medium
- Remote Code InclusionCAPEC-253
- Force Use of Corrupted FilesCAPEC-263Medium
- Open-Source Library ManipulationCAPEC-538likelihood: Low · High
ATT&CK techniques
- Process InjectionT1055
- Browser ExtensionsT1176
- Supply Chain Compromise: Software Dependencies and Development ToolsT1195.001
- Server Software Component: IIS ComponentsT1505.004
- Server Software Component: Terminal Services DLLT1505.005
- Hijack Execution Flow: Dynamic Linker HijackingT1574.006
- Hijack Execution Flow: KernelCallbackTableT1574.013
- Reflective Code LoadingT1620
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.