Quick answers
- Is CVE-2026-62852 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62852 being exploited in the wild.
- How severe is CVE-2026-62852?
- Medium severity, with a CVSS score of 6.5, published 6 November 2026.
- Which products and versions are affected?
- FreeScout before 1.8.226.
- Is there a fix for CVE-2026-62852?
- 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-62852 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-62852?
- 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 RealtimeConvNewThread Polycast event handler in FreeScout prior to 1.8.226 performs mailbox-level access checks but fails to enforce conversation-level restrictions. An authenticated user configured to view only assigned conversations can subscribe to predictable conv.<conversation_id> channels to receive event payloads containing complete thread data, attachments with valid download tokens, and metadata for conversations they should not access. The fix adds conversation-level authorization checks using Laravel's policy-based authorization.
Affected products
- FreeScout FreeScout before 1.8.226
Timeline
- 2026-11-06: disclosed