# CVE-2026-47196: Quest Bot: Empty automod rule causes every guild message to be deleted

> An attacker can delete all guild messages by adding an empty automod rule, causing a denial of service in Quest Bot.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-fgwg-6px5-cxp5

## What is CVE-2026-47196?

CVE-2026-47196 is a high-severity vulnerability in duck-organization questbot, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Quest Bot is an opensource Discord Bot. Prior to version 1.1.6, the automod add command trims user input but does not reject an empty result. Adding a rule containing only whitespace stores an empty word. The message listener later checks content.includes(""), which is always true, causing the bot to delete every non-bot guild message. This issue has been patched in version 1.1.6.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-47196 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47196 is a high-severity vulnerability in duck-organization questbot, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47196 exists.

Affected product: duck-organization questbot. 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-47196/ (Markdown: https://insights.sbomify.com/CVE-2026-47196/index.md)
```

## Sources

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

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