Quick answers
- Is CVE-2026-27851 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-27851 being exploited in the wild.
- How severe is CVE-2026-27851?
- High severity, with a CVSS score of 7.4, published 12 May 2026.
- Which products and versions are affected?
- Open-Xchange Dovecot CE 2.4.0 through 2.4.3; Open-Xchange Dovecot Pro 2.3.0 through 3.1.4.
- Is there a fix for CVE-2026-27851?
- A patch was published on 2026-05-05: Initial internal release of fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-27851 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-27851?
- Check whether you run Dovecot, Open-Xchange Dovecot CE or 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
A vulnerability exists in Dovecot's variable expansion mechanism where the use of the 'safe' filter incorrectly marks all subsequent pipelines on the same string as safe. This logic error allows unescaped, malicious data to be processed by the application. If these strings are used in authentication queries, an attacker can perform SQL or LDAP injection. The attack requires a specific configuration (use of the safe filter) and has high complexity, but can be executed remotely without prior authentication. Fixes are available in Dovecot Pro 3.1.5 and Dovecot CE 2.4.4.
Affected products
- Open-Xchange Dovecot Pro 2.3.0 through 3.1.4
- Open-Xchange Dovecot CE 2.4.0 through 2.4.3
Timeline
- 2026-03-29: other: Vulnerability discovered
- 2026-05-05: patched: Initial internal release of fix
- 2026-05-12: disclosed: Public advisory released