CVE-2026-62851: freescout · Information Exposure
Affects freescoutSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.8.226 when convenient.
Data as of 6 Nov 2026, 17:19 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 1.8.226
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 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 6 Nov 2026.
What to do
Upgrade freescout to 1.8.226.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| freescout-help-deskfreescout | Affected
| Fixed in
|
Description
FreeScout is a self-hosted help desk and shared mailbox. Prior to 1.8.226, the search-by-number shortcut in ConversationsController::search() resolves a user-controlled ticket number without applying the mailbox filter or view policy used by the normal search path. An authenticated non-admin agent who is a member of at least one mailbox can request /search with a hash-prefixed ticket number and use the 302 Location header to confirm that a conversation exists in a different mailbox the agent cannot access and learn its internal conversation and folder identifiers. The destination conversation remains protected, so this issue does not disclose message content, attachments, or customer data. This issue is fixed in version 1.8.226.