Servers and applications
CVE-2026-40016
Attacker can upload a malicious Sieve script over ManageSieve service (or locally) to bypass configured CPU time limits for Sieve up to 130 times of the configured limit. Attacker can use this to degrade server performance and bypass configured CPU time limits for Sieve scripts. Install fixed version, or alternatively prevent direct access to Sieve scripts via ManageSieve or local access. No…
- Severity
- Medium 6.5
- Published
- 12 May 2026
- Last changed
- 26 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.4.4
- Exploit chance
- 0.3% in the next 30 daysHigher than 27% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Sources
- NVD
Description
Attacker can upload a malicious Sieve script over ManageSieve service (or locally) to bypass configured CPU time limits for Sieve up to 130 times of the configured limit. Attacker can use this to degrade server performance and bypass configured CPU time limits for Sieve scripts. Install fixed version, or alternatively prevent direct access to Sieve scripts via ManageSieve or local access. No publicly available exploits are known.
Affected software
| Software | Affected versions |
|---|---|
DovecotServers and applications · cpe:a:dovecot:dovecot |
|
About Dovecot
free software IMAP and POP3 server
- Developer
- Timo SirainenWikidata
- License
- MIT License, GNU Lesser General Public License, version 2.1Wikidata
- Written in
- CWikidata
- First released
- 2002Wikidata
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 2.4 | 2.4.5 | Yes |
| 2.3 | 2.3.21.1 | Yes |
| 2.2 | 2.2.36.4 | Ended 24 Jan 2025 |
| 2.1 | 2.1.16 | Ended 22 Dec 2017 |
| 2.0 | 2.0.15 | Ended 11 Apr 2013 |
From endoflife.date.
Vulnerabilities in Dovecot
- In our list
- 68
- Published in the last 12 months
- 16
- Critical, last 12 months
- 1
- High, last 12 months
- 5
- Known exploited
- 0
- CVE-2026-42006An attacker can cause uncontrolled memory usage with excessive bracing over IMAP. The fix in CVE-2026-27857 was incomplete, only blocking one way of doing this, so there was still another way left open. In particular, the fix was for closing braces, but you could still use open braces to bypass the limit. Using excessive bracing, attacker can cause memory usage up to configured memory limit.…Medium 4.3 12 May 2026
- CVE-2026-40020Attacker can use the IMAP SETACL command to inject the anyone permission to user's dovecot-acl file even if imap_acl_allow_anyone=no. This causes folders to be spammed to all users. The impact is limited to being able to spam folders to other users, no unexpected access is gained. Install to fixed version. No publicly available exploits are known.Medium 4.3 12 May 2026
- CVE-2026-33603Attacker can use a specially crafted base64 exchange between Dovecot and Client to fake SCRAM TLS channel binding. This requires that the attacker is able to position itself between Dovecot and the client connection. If successful, the attacker can eavesdrop communications between Dovecot and client as MITM proxy. Install fixed version. No publicly available exploits are known.Medium 5.3 12 May 2026
- CVE-2026-27851When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabling unsafe data to be unescaped. This can enable SQL / LDAP injection attacks when used in authentication. Avoid using safe filter until on fixed version. No publicly available exploits are known.Critical 9.1 12 May 2026
- CVE-2026-27860If auth_username_chars is empty, it is possible to inject arbitrary LDAP filter to Dovecot's LDAP authentication. This leads to potentially bypassing restrictions and allows probing of LDAP structure. Do not clear out auth_username_chars, or install fixed version. No publicly available exploits are known.Medium 5.3 27 Mar 2026
- CVE-2026-27859A mail message containing excessive amount of RFC 2231 MIME parameters causes LMTP to use too much CPU. A suitably formatted mail message causes mail delivery process to consume large amounts of CPU time. Use MTA capabilities to limit RFC 2231 MIME parameters in mail messages, or upgrade to fixed version where the processing is limited. No publicly available exploits are known.Medium 5.3 27 Mar 2026