CVE-2026-85749: MailWatch · Authorization Bypass Through User-Controlled SQL Primary Key
Affects MailWatchSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 1.2.27 soon.
Data as of 28 Oct 2026, 22:58 UTC
- Patch
- Available – fixed in 1.2.27
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade MailWatch and mailwatch/MailWatch to 1.2.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mailwatchMailWatch | Affected
| Fixed in
|
GitHubmailwatch/MailWatchpkg:github/mailwatch/MailWatchOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade MailWatch for MailScanner to version 1.2.27 or later, where this authorization bypass vulnerability is fixed. No other mitigation is required as the fix addresses the core issue of missing ownership checks on quarantine actions.
Description
MailWatch for MailScanner versions prior to 1.2.27 contain an authorization bypass vulnerability. Authenticated users with low privileges can release or permanently delete quarantined emails belonging to other users or domains by manipulating the message ID parameter. This occurs because the application does not verify message ownership when processing quarantine actions, despite requiring a valid session and CSRF token. The vulnerability is fixed in version 1.2.27.