CVE-2026-61840: vantern-org questbot · Server-Side Request Forgery
Affects vantern-org questbotSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.1.9 when convenient.
Data as of 30 Oct 2026, 20:38 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 1.1.9
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade vantern-org questbot to 1.1.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vantern-orgquestbot | Affected
| Fixed in
|
AI-suggested
Upgrade Quest Bot to version 1.1.9 or later, where this SSRF vulnerability is fixed. No additional mitigation is required as the fix addresses the root cause of the issue.
Description
CVE-2026-61840 is a server-side request forgery (SSRF) vulnerability in the open-source Discord bot Quest Bot prior to version 1.1.9. The flaw arises from the 'image to GIF' command, which performs hostname validation against public IP addresses but then makes requests by hostname, allowing a second DNS lookup. This enables DNS rebinding attacks where an attacker-controlled domain can bypass internal address protections. The vulnerability allows any server member to trigger the flaw without special permissions. Requests are limited to HTTPS on port 443 and only return genuine image content, limiting impact to blind internal probing and limited image retrieval from internal endpoints. The issue is fixed in version 1.1.9.