<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Postfix on kalfaoglu.net</title><link>https://blog.kalfaoglu.net/tags/postfix/</link><description>Recent content in Postfix on kalfaoglu.net</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kalfaoglu.net/tags/postfix/index.xml" rel="self" type="application/rss+xml"/><item><title>Postfix 3.11.2 Patches a 20-Year-Old Buffer Over-Read — and an AI Found Most of the Rest</title><link>https://blog.kalfaoglu.net/posts/2026-05-07-postfix-3112-cve-2026-43964-en/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://blog.kalfaoglu.net/posts/2026-05-07-postfix-3112-cve-2026-43964-en/</guid><description>&lt;p&gt;On May 4, 2026, Wietse Venema released Postfix 3.11.2, 3.10.9, 3.9.10, and 3.8.16. If you run a mail server, this is the update you actually want to read — not because the CVSS score is alarming (it isn&amp;rsquo;t), but because one of the bugs patched in this release has been sitting in the codebase since 2005.&lt;/p&gt;
&lt;h2 id="the-cve-worth-knowing-about"&gt;The CVE Worth Knowing About&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://cve.threatint.eu/CVE/CVE-2026-43964"&gt;CVE-2026-43964&lt;/a&gt; is an off-by-one error in how Postfix handles enhanced status codes. If an SMTP access table, policy server, DNSBL response, or milter returns a bare status code — something like &lt;code&gt;5.7.2&lt;/code&gt; without any text following it — the daemon reads past the end of the allocated buffer. The result is a process crash.&lt;/p&gt;</description></item></channel></rss>