Quick answers
- Is CVE-2026-33603 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33603 being exploited in the wild.
- How severe is CVE-2026-33603?
- Medium severity, with a CVSS score of 6.8, published 12 May 2026.
- Which products and versions are affected?
- Open-Xchange Dovecot CE 2.4.0, 2.4.3; Open-Xchange Dovecot Pro 2.3.0, 3.0.5, 3.1.0, 3.1.4.
- Is there a fix for CVE-2026-33603?
- 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-33603 attacked?
- It is attacked from the adjacent network, in a software library.
- Am I affected by CVE-2026-33603?
- 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 implementation of SCRAM authentication where an attacker can craft a malicious base64 exchange to spoof TLS channel binding. The flaw is categorized as improper control of resource identifiers (CWE-99). To exploit this, an attacker must be able to position themselves between the Dovecot server and the client (Man-in-the-Middle). If successful, the attacker can bypass the integrity protection provided by channel binding, allowing them to decrypt and eavesdrop on the communication session. The vulnerability is addressed in Dovecot Pro 3.1.5 and Dovecot CE 2.4.4.
Affected products
- Open-Xchange Dovecot Pro 2.3.0, 3.0.5, 3.1.0, 3.1.4
- Open-Xchange Dovecot CE 2.4.0, 2.4.3
Timeline
- 2026-05-05: patched: Initial internal release of fix
- 2026-05-12: disclosed: Public advisory published