Linux · Ubuntu · Package update · April 15, 2026

dovecot-pgsql 1:2.3.16+dfsg1-3ubuntu2.7: dovecot-pgsql 1:2.3.16+dfsg1-3ubuntu2.7 for Ubuntu 22.04.1 LTS (jammy)

dovecot-pgsql 1:2.3.16+dfsg1-3ubuntu2.7, released April 15, 2026, fixes 8 CVEs in dovecot-pgsql. None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
7.5
Base score, 0 to 10
Highest EPSS
0.0080
57th percentile

Priority of the 8 CVEs

Patch now 0 Urgent 0 High 3 Routine 5

Fixed package versions

ProductReleaseFixed in
dovecot-pgsqlUbuntu 22.04.1 LTS (jammy)1:2.3.16+dfsg1-3ubuntu2.7

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2026-27858 dovecot23: pigeonhole: managesieve-login can allocate large amount of memory during authentication (bsc#1260901).7.5 0.0080 None reported
High CVE-2025-59032 dovecot23: pigeonhole: ManageSieve panic occurs with sieve-connect as a client (bsc#1260902).7.5 0.0073 None reported
High CVE-2026-27857 dovecot23: sending excessive parenthesis causes imap-login to use excessive memory (bsc#1260898).7.5 0.0068 None reported
Routine CVE-2026-0394 dovecot-sqlite: When dovecot has been configured to use per-domain passwd files, and they are placed one path component above /etc, o...5.3 0.0044 None reported
Routine CVE-2026-27856 dovecot23: Doveadm credentials were not checked using timing-safe checking function (bsc#1260899).5.9 0.0040 None reported
Routine CVE-2026-27859 dovecot23: excessive RFC 2231 MIME parameters in email would can excessive CPU usage (bsc#1260897).5.3 0.0038 None reported
Routine CVE-2026-27855 dovecot23: OTP driver vulnerable to replay attack (bsc#1260900).5.9 0.0032 None reported
Routine CVE-2025-59031 dovecot23: decode2text.sh OOXML extraction may follow symlinks and read unintended files during indexing4.3 0.0029 None reported
Showing 1 to 8 of 8 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.