# CVE-2026-85749 — MailWatch

> As of 2026-10-29, CVE-2026-85749 is a HIGH-severity vulnerability in MailWatch, CVSS v3.1 8.1, EPSS 0.2% (21.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-85749 as of 2026-10-29; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-29

## What is CVE-2026-85749?

MailWatch for MailScanner is a web-based front-end to MailScanner. Prior to 1.2.27, any authenticated MailWatch user, including the U/user, D/domain-admin, and H/host roles, can release to inbox or permanently delete the quarantined mail of any other user or domain by supplying an arbitrary message `id` to `mailscanner/quarantine_action.php`. The action path calls `quarantine_list_items()` in `mailscanner/functions.php`, which selects from `maillog` by the supplied identifier without the per-role `global_filter` applied by listing and read views. The action requires a valid session and CSRF token, but the caller can submit a token from the caller's own session; ownership of the requested message is never checked. Message identifiers are enumerable, allowing a low-privilege user to invoke `quarantine_release()` or `quarantine_delete()` for other users' or domains' quarantined messages, force-delivering mail held by the quarantine or permanently deleting it. This issue is fixed in version 1.2.27.

The record classifies CVE-2026-85749 under weakness classes [CWE-566](https://cwe.mitre.org/data/definitions/566.html), [CWE-639](https://intel.threadlinqs.com/cwe/CWE-639). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 22 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.1 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 21.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-28

## Is CVE-2026-85749 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **mailwatch**: MailWatch

## How to fix CVE-2026-85749

No vendor patch reference has been recorded for CVE-2026-85749 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-85749

No threat campaign in the Threadlinqs corpus currently references CVE-2026-85749, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/mailwatch/MailWatch/security/advisories/GHSA-w7v5-7g6w-87r4)

**Other references**

- [github.com](https://github.com/mailwatch/MailWatch/commit/bc04f25eb0cec028cbd4ded9c049cfc6f663a15f)
- [github.com (v1.2)](https://github.com/mailwatch/MailWatch/releases/tag/v1.2.27)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-85749
No Threadlinqs detection currently covers CVE-2026-85749; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
