Skip to main content
VulnerabilityPublished

CVE-2025-59028: Open-Xchange OX Dovecot Pro · Improper Input Validation

Affects Open-Xchange OX Dovecot ProSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Open-Xchange GmbHOX Dovecot ProAffected
  • <=3.1.0
  • <=2.4.0
Fixed in–

AI-suggested

A fixed version of OX Dovecot Pro addressing this vulnerability should be installed when available. Alternatively, concurrency in login processes can be disabled to mitigate the issue, but this results in significant performance degradation in large deployments. Patch status is not explicitly confirmed in the provided data; users should monitor the vendor advisory for official fixes.

Description

CVE-2025-59028 is a medium severity vulnerability in Open-Xchange GmbH's OX Dovecot Pro where improper input validation of base64 SASL data causes the login process to disconnect from the authentication server. This results in denial of service by breaking all active authentication sessions and preventing concurrent logins. No public exploits are known. Mitigation involves installing a fixed version or disabling concurrency in login processes, though the latter causes significant performance degradation in large deployments.

References

Community reviews

Loading reviews…