CVE-2026-27855: Open-Xchange OX Dovecot Pro · Authentication Bypass by Capture-replay
Affects Open-Xchange OX Dovecot ProSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Open-Xchange GmbHOX Dovecot Pro | Affected
| Fixed in– |
AI-suggested
Mitigation involves disabling authentication cache or avoiding username alterations in passdb that lead to caching OTP credentials. Additionally, ensure authentication occurs over secure channels by switching to SCRAM protocol or OAUTH2 where possible. Securing communications to prevent interception of OTP exchanges is critical. Monitor vendor advisories for updates on official fixes.
Description
CVE-2026-27855 is a medium severity vulnerability in Open-Xchange GmbH's OX Dovecot Pro affecting its OTP authentication mechanism. Under specific conditions—when authentication cache is enabled and the username is altered in the password database—OTP credentials can be cached, allowing replay of the same OTP response. An attacker who can observe an OTP exchange may reuse it to log in as the user. The vulnerability is mitigated by using secure communication protocols such as SCRAM or OAUTH2 or by securing the communication channel. No public exploits are known at this time.