# CVE-2026-47177: Quest Bot: Ticket transcripts can disclose private ticket contents to a lower-visibility channel

> A malicious admin can leak private ticket contents to a public channel by misconfiguring the transcript destination, exposing sensitive user data.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** GHSA-4rpv-95pj-6ccg

## What is CVE-2026-47177?

CVE-2026-47177 is a medium-severity vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Quest Bot is an opensource modern Discord Bot built for moderation, utilities and support. Prior to version 1.0.4, a user who can configure bot settings can set the ticket transcript channel to a channel they can read. When tickets are closed, the bot exports the full ticket history and sends it to that configured transcript channel. This can expose private ticket messages to users who could not read the original ticket channel. This issue has been patched in version 1.0.4.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-47177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47177 is a medium-severity vulnerability in duck-organization quest-bot, published on 11 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47177 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-47177/ (Markdown: https://insights.sbomify.com/CVE-2026-47177/index.md)
```

## Sources

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

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