CVE-2026-27856: Doveadm credentials are verified using direct comparison which is susceptible to timing oracle attack.
Doveadm credentials are verified using direct comparison which is susceptible to timing oracle attack. An attacker can use this to determine the configured credentials. Figuring out the credential will lead into full access to the affected component. Limit access to the doveadm http service port, install fixed version. No publicly available exploits are known.
Security readout for executives and security teams
Plain-English summary
CVE-2026-27856 affects doveadm credential checking in OX Dovecot Pro. Because credentials are compared directly, a remote attacker may be able to infer the configured credential through timing differences. Successful recovery could give full access to the affected component.
Executive priority
Treat this as a high-priority administrative-service exposure issue. Prioritize externally reachable or broadly reachable doveadm HTTP services first, because credential recovery could lead to full component access even though public exploit evidence is not reported.
Technical view
The issue is a timing oracle in doveadm HTTP credential verification, mapped to CWE-208 and CWE-287. CVSS 3.1 is 7.4 high: network reachable, unauthenticated, high attack complexity, no user interaction, with high confidentiality and integrity impact.
Likely exposure
Exposure is most likely where the doveadm HTTP service port is enabled and reachable by untrusted networks. The source bundle names OX Dovecot Pro, but exact affected version detail is sparse and should be validated against vendor CSAF and Red Hat advisories.
Exploitation context
The provided record says no publicly available exploits are known. CISA KEV status is false, so active exploitation should not be assumed from these sources. Exploitation appears constrained by high complexity, but the impact is serious if credentials are recovered.
Researcher notes
Evidence supports a timing side-channel in direct credential comparison, not a broadly weaponized exploit. The affected-version data in the bundle is limited, including an ambiguous version value, so researchers should rely on vendor CSAF and Red Hat errata for exact applicability.
Mitigation direction
Limit access to the doveadm HTTP service port to trusted administrative networks.
Install the fixed vendor version when applicable to your deployment.
Review Open-Xchange and Red Hat advisories for exact package applicability.
Disable unnecessary doveadm HTTP exposure if operationally feasible.
Monitor authentication and administrative access logs for unusual activity.
Validation and detection
Inventory OX Dovecot Pro and Red Hat-packaged Dovecot deployments.
Confirm whether the doveadm HTTP service is enabled.
Check whether the doveadm HTTP port is reachable from untrusted networks.
Compare installed versions against vendor CSAF and Red Hat errata.
Verify firewall or access-control restrictions around administrative service ports.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-208: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-208 · source CWE mapping
Observable Timing Discrepancy
Observable Timing Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.