# CVE-2026-47169: Quest Bot: Manage Server users can configure AutoRole to grant Administrator to controlled joining accounts

> A user with Manage Server permissions can configure AutoRole to grant Administrator privileges to joining accounts, leading to full server takeover.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-8vgg-4hpx-7qfg

## What is CVE-2026-47169?

CVE-2026-47169 is a high-severity vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.3, a user with Manage Server / ManageGuild, but without Manage Roles or Administrator, can configure the bot’s AutoRole feature to assign an arbitrary role to new members. If the selected role has Administrator and is below the bot’s highest role, the attacker can join with a controlled account and receive full server admin. This issue has been patched in version 1.0.3.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-47169?


## How do I fix CVE-2026-47169?

No fix has been published for CVE-2026-47169 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47169 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47169 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47169 and fix it if it is affected.

What it is: CVE-2026-47169 is a high-severity vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47169 exists.

Affected product: duck-organization quest-bot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47169/ (Markdown: https://insights.sbomify.com/CVE-2026-47169/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47169
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47169
- OSV: https://osv.dev/vulnerability/CVE-2026-47169

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47169/
Summaries are generated and may contain mistakes; the official description above is the record.