Authentication bypass via trusted-proxy field injection
Published Aug 28, 2026 · Updated Aug 28, 2026
Authentication bypass in Open-Xchange OX Dovecot CE and Pro allows trusted-proxy hosts to authenticate as any user without a password. XCLIENT forwarding fails to namespace a bare proxy-supplied token separately from internal authentication fields, allowing nopassword field injection. Exposure requires a configured trusted proxy and a password database that honors the injected passwordless-authentication field.
Summary
What happened
Authentication bypass in Open-Xchange OX Dovecot CE and Pro allows trusted-proxy hosts to authenticate as any user without a password. XCLIENT forwarding fails to namespace a bare proxy-supplied token separately from internal authentication fields, allowing nopassword field injection. Exposure requires a configured trusted proxy and a password database that honors the injected passwordless-authentication field.
The record
- CVE
- CVE-2026-42008
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Open-Xchange GmbH
- Product
- OX Dovecot CE
- Classifications
- CWE-287, T1078
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.3.4 <2.4.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo