Is Postfix 2.8.20 affected?
Feb 8, 2015 · Release notes ↗
3 known vulnerabilities affect 2.8.20 (highest CVSS 7.8).
Your branch 2.8 has reached end of life (Feb 8, 2015).
15 newer releases in its track, up to 3.11.7. What changed up to 3.11.7
Vulnerabilities affecting 2.8.20
- 7.8 CVE-2017-10140 Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and la… fixed in 2.11.10
- 5.3 CVE-2023-51764 Postfix through 3.8.5 allows SMTP smuggling unless configured with smtpd_data_restrictions=reject_unauth_pipelining and smtpd_discard_ehlo_keywords=chunking (or certain other options that exist in… fixed in 3.5.23
- 3.7 CVE-2026-43964 Postfix before 3.8.16, 3.9 before 3.9.10, and 3.10 before 3.10.9 sometimes allows a buffer over-read and process crash via an enhanced status code that lacks text after the third number. fixed in 3.8.16
Newer releases
| 3.11.7 | Sep 8, 2026 | 2.8.20 → 3.11.7 |
| 3.10.14 | Sep 8, 2026 | 2.8.20 → 3.10.14 |
| 3.9.15 | Sep 8, 2026 | 2.8.20 → 3.9.15 |
| 3.8.21 | Sep 8, 2026 | 2.8.20 → 3.8.21 |
| 3.7.23 | Sep 8, 2026 | 2.8.20 → 3.7.23 |
| 3.6.21 | Sep 8, 2026 | 2.8.20 → 3.6.21 |
| 3.5.28 | Sep 8, 2026 | 2.8.20 → 3.5.28 |
| 3.4.29 | Apr 19, 2023 | 2.8.20 → 3.4.29 |
| 3.3.22 | Feb 6, 2022 | 2.8.20 → 3.3.22 |
| 3.2.22 | Apr 12, 2021 | 2.8.20 → 3.2.22 |
| 3.1.15 | Feb 3, 2020 | 2.8.20 → 3.1.15 |
| 3.0.15 | Feb 26, 2019 | 2.8.20 → 3.0.15 |
| 2.11.11 | Jan 28, 2018 | 2.8.20 → 2.11.11 |
| 2.10.10 | May 15, 2016 | 2.8.20 → 2.10.10 |
| 2.9.15 | Oct 10, 2015 | 2.8.20 → 2.9.15 |