Is CVE-2026-62851 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62851 being exploited in the wild.

How severe is CVE-2026-62851?

Medium severity, with a CVSS score of 4.3, published 6 November 2026.

Is there a fix for CVE-2026-62851?

Yes: fixed in 1.8.226. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-62851 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-62851?

Check whether you run FreeScout at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62851: FreeScout conversation search access control bypass

CVE-2026-62851 · Severity: medium · CVSS 4.3 · Published 2026-11-06

FreeScout is a self-hosted help desk and shared mailbox platform. Prior to version 1.8.226, an authenticated agent can use a ticket number shortcut to bypass mailbox access controls and confirm the existence of conversations in mailboxes they are not permitted to access, learning internal conversation and folder identifiers. While the conversation content remains protected, this information disclosure allows agents to map the help desk structure they should not see.

Technologies: FreeScout. Vendors: FreeScout.

Quick answers

Is CVE-2026-62851 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62851 being exploited in the wild.
How severe is CVE-2026-62851?: Medium severity, with a CVSS score of 4.3, published 6 November 2026.
Which products and versions are affected?: FreeScout prior to 1.8.226.
Is there a fix for CVE-2026-62851?: Yes: fixed in 1.8.226. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62851 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-62851?: Check whether you run FreeScout at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.8.226

Technical details

The search() method in ConversationsController fails to apply mailbox and view policies when resolving a ticket number prefixed with a hash symbol, unlike the standard search path. An authenticated agent with membership in at least one mailbox can exploit this by sending a request with a hash-prefixed ticket number and observing the 302 redirect response header to determine whether a conversation exists in another mailbox and extract its internal identifiers. The fix adds a permission check before returning the conversation result.

Affected products

FreeScout FreeScout prior to 1.8.226

Timeline

2026-11-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.