CVE-2026-27857: Open-Xchange OX Dovecot Pro · Uncontrolled Resource Consumption
Affects Open-Xchange OX Dovecot ProSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation 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– |
Red Hatredhat/ox-dovecot-propkg:rpm/redhat/ox-dovecot-proOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fixed version of OX Dovecot Pro is available and should be installed to remediate this vulnerability. The Red Hat advisory (RHSA-2026:26564) provides updated packages for Red Hat Enterprise Linux 7 Extended Lifecycle Support. No other mitigations are recommended or effective. Administrators should apply the official security update promptly to prevent denial of service conditions. There are no known workarounds or temporary fixes.
Description
Sending "NOOP (((...)))" command with 4000 parenthesis open+close results in ~1MB extra memory usage. Longer commands will result in client disconnection. This 1 MB can be left allocated for longer time periods by not sending the command ending LF. So attacker could connect possibly from even a single IP and create 1000 connections to allocate 1 GB of memory, which would likely result in reaching VSZ limit and killing the process and its other proxied connections. Attacker could connect possibly from even a single IP and create 1000 connections to allocate 1 GB of memory, which would likely result in reaching VSZ limit and killing the process and its other proxied connections. Install fixed version, there is no other remediation. No publicly available exploits are known.
References
- documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0001.json (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-27857 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2452179 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27857.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:26564 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:17602 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:13498 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19149 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:13830 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19455 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19453 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:18053 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:17630 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:17628 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:17625 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:17626 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:13857 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:19364 (opens in a new tab)