Back

MEDIUM

dovecot: Dovecot: Authentication bypass via trusted proxy forwarding

Published Aug 28, 2026

Description

Forwarding information received from a host listed as a trusted proxy is not kept separate from Dovecot's own authentication fields, so a value sent by that host can be injected as an internal authentication field. Any host permitted to act as a trusted proxy can authenticate as any user without knowing that user's password. This affects deployments whose password database honours a field that permits authentication without a password. Deployments that do not configure trusted proxies are not affected. Restrict the list of trusted proxy networks to hosts that are fully under your control. Update to non-vulnerable version. No publicly available exploits are known.

Affected products

Remediation

Red Hat mitigation

To mitigate this issue, ensure that the `auth_proxy_trusted_networks` configuration in Dovecot is strictly limited to only trusted hosts that are fully under administrative control. Review and restrict the `auth_proxy_trusted_networks` setting in your Dovecot configuration (e.g., `/etc/dovecot/conf.d/10-auth.conf` or similar) to prevent unauthorized hosts from acting as trusted proxies. If trusted proxies are not required, remove this configuration entirely. A restart of the Dovecot service may be required for changes to take effect.

References (6)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner OX
Published Aug 28, 2026
Updated Aug 28, 2026
Reserved Apr 23, 2026
CISA Vulnrichment
Updated Aug 28, 2026
NVD
Status Deferred
Modified Sep 3, 2026
Red Hat
Severity Moderate
Public date Aug 28, 2026
ENISA EUVD
Assigner OX
Published Aug 28, 2026
Updated Aug 28, 2026
Exploited since n/a
EUVD-2026-67673