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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon Linux Ami 2 | — | Upgrade dovecot-pigeonholeUpgrade dovecot-develUpgrade dovecot-pgsqlUpgrade dovecotUpgrade dovecot-mysqlUpgrade dovecot-debuginfo | Oct 19, 2026 | Oct 19, 2026 |
| Amazon_linux_2023 | — | Upgrade dovecot-pigeonhole-debuginfoUpgrade dovecot-develUpgrade dovecot-mysql-debuginfoUpgrade dovecot-pigeonholeUpgrade dovecot-pgsql-debuginfoUpgrade dovecot-pgsqlUpgrade dovecot-debugsourceUpgrade dovecot-mysqlUpgrade dovecot-debuginfoUpgrade dovecot | Sep 30, 2026 | Aug 28, 2026 |
| Debian | — | Upgrade dovecot | Sep 30, 2026 | Aug 28, 2026 |
| Redhat_linux | — | No solution exists | Sep 2, 2026 | Aug 28, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub