Quick answers
- Is CVE-2026-49217 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49217 being exploited in the wild.
- How severe is CVE-2026-49217?
- High severity, with a CVSS score of 7.5, published 20 August 2026.
- Which products and versions are affected?
- Mailu prior to 2024.06.52.
- Is there a fix for CVE-2026-49217?
- A patch was published on 2026-06-52: Patched in Mailu 2024.06.52 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49217 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-49217?
- Check whether you run Mailu 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.
Technical details
The vulnerability is a missing authentication check (CWE-306) in the PATCH /api/v1/token/<id> endpoint of the Mailu admin REST API. An unauthenticated attacker can exploit this over the network to modify any existing user token by removing IP restrictions or updating comment fields, provided the REST API is enabled. The attack requires no privileges, user interaction, or special preconditions beyond network reachability to the REST API. The fix is available in Mailu version 2024.06.52 and later, or administrators can disable the REST API as a workaround.
Affected products
- Mailu Mailu prior to 2024.06.52
Timeline
- 2026-05-28: disclosed: GHSA advisory published
- 2026-06-52: patched: Patched in Mailu 2024.06.52