Quick answers
- Is CVE-2026-113599 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113599 being exploited in the wild.
- How severe is CVE-2026-113599?
- Medium severity, with a CVSS score of 5.4, published 20 October 2026.
- Which products and versions are affected?
- Modoboa before 2.8.0.
- Is there a fix for CVE-2026-113599?
- Yes: fixed in 2.8.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113599 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113599?
- Check whether you run Modoboa 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: 2.8.0
Technical details
The ARMessageSerializer in the auto-reply API does not properly validate that the authenticated user owns the mailbox they are modifying. An attacker can POST to /api/v2/armessages/ with another user's mbox identifier to create or modify auto-reply messages, subject and content for arbitrary mailboxes. The lack of ownership checks on the mbox field allows privilege escalation within the application.
Affected products
- Modoboa Modoboa before 2.8.0
Timeline
- 2026-10-20: disclosed
- 2026-02-26: patched: Commit e0a4e3b fixes the issue per GitHub