Skip to main content
VulnerabilityPublished

CVE-2026-0394: Open-Xchange OX Dovecot Pro · Path Traversal

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, 06:59 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 37% 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:L/I:N/A:N

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 29 Oct 2026.

What to do

Affected software

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

AI-suggested

Upgrade to a fixed version of OX Dovecot Pro when available. Alternatively, use an authentication scheme that does not rely on path-based per-domain passwd files. Another mitigation is to ensure per-domain passwd files are stored in a secure directory such as /etc/dovecot/auth/%d, avoiding placement one directory above /etc or allowing slashes in domain components.

Description

CVE-2026-0394 is a medium severity path traversal vulnerability in Open-Xchange GmbH's OX Dovecot Pro. It occurs when dovecot is configured to use per-domain passwd files placed one directory above /etc or when slash is allowed in domain components, enabling unintended reading of sensitive files like /etc/passwd. This can lead to incorrect authentication or unexpected validation of system users. No public exploits are known. Mitigation involves upgrading to a fixed version, using a different authentication scheme that does not rely on paths, or relocating per-domain passwd files to a safer directory such as /etc/dovecot/auth/%d.

References

Community reviews

Loading reviews…