Quick answers
- Is CVE-2026-52681 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52681 being exploited in the wild.
- How severe is CVE-2026-52681?
- Low severity, with a CVSS score of 3.1, published 28 August 2026.
- Which products and versions are affected?
- Open-Xchange Dovecot Pro 2.3.0 to 2.3.22.1, 3.0.0 to 3.0.6, 3.1.0 to 3.1.5.
- Is there a fix for CVE-2026-52681?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-52681 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-52681?
- Check whether you run Open-Xchange Dovecot Pro 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 resource accounting bypass in the Sieve script engine. CPU usage is tracked per compiled script object, and an authenticated attacker can reset the accounting by repeatedly changing the active Sieve script; each script change creates a new compiled script object with zeroed counters. Additionally, compiled script files are not removed when scripts are deleted or renamed, leading to disk space exhaustion over time. The attacker requires valid mail account credentials to change their Sieve scripts, making this an authenticated attack. The combined effects allow sustained CPU consumption beyond configured limits and increased disk I/O contention, degrading mail delivery service. Patches are available in OX Dovecot Pro 2.3.22.2, 3.0.7, and 3.1.6 or later.
Affected products
- Open-Xchange Dovecot Pro 2.3.0 to 2.3.22.1, 3.0.0 to 3.0.6, 3.1.0 to 3.1.5
Timeline
- 2026-08-28: disclosed