{"id":895,"date":"2026-05-12T18:53:15","date_gmt":"2026-05-12T18:53:15","guid":{"rendered":"https:\/\/thedigitalfortress.us\/?p=895"},"modified":"2026-05-12T18:53:15","modified_gmt":"2026-05-12T18:53:15","slug":"new-exim-bdat-vulnerability-exposes-gnutls-builds-to-potential-code-execution","status":"publish","type":"post","link":"https:\/\/thedigitalfortress.us\/?p=895","title":{"rendered":"New Exim BDAT Vulnerability Exposes GnuTLS Builds to Potential Code Execution"},"content":{"rendered":"<div>\n<p><span class=\"p-author\"><i class=\"icon-font icon-user\">\ue804<\/i><span class=\"author\">Ravie Lakshmanan<\/span><i class=\"icon-font icon-calendar\">\ue802<\/i><span class=\"author\">May 12, 2026<\/span><\/span><span class=\"p-tags\">Vulnerability \/ Email Security<\/span><\/p>\n<\/div>\n<div id=\"articlebody\">\n<div class=\"separator\" style=\"clear: both;\"><a href=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEgrSn3emm_NbwXDi3elR0wo5ErHhg-gPT4-u4zk7MHZg4u0ruMmj2_KGgPF8fz06Riv6Gu5NXMN3eBP8H5bVf6dmvOz-lvb-qrvhLlssLUzl97ZVmIWoIOmMPOGrupv864dt0d4V_dxgaaxYYNuy2z9rbZMWIOcjlwZaiifq4-ktRqlEBCJ6a_m3MFiwq65\/s1700-e365\/exim.jpg\" style=\"display: block;  text-align: center; clear: left; float: left;\"><\/a><\/div>\n<p>Exim has released security updates to address a severe security issue affecting certain configurations that could enable memory corruption and potential code execution.<\/p>\n<p><a href=\"https:\/\/www.exim.org\/exim-html-current\/doc\/html\/spec_html\/index.html\">Exim<\/a> is an open-source Mail Transfer Agent (MTA) designed for Unix-like systems to receive, route, and deliver email.<\/p>\n<p>The vulnerability, tracked as CVE-2026-45185, aka Dead.Letter, has been described as a use-after-free vulnerability in Exim&#8217;s binary data transmission (BDAT) message body parsing when a TLS connection is handled by GnuTLS.<\/p>\n<p>\u00abThe vulnerability is triggered during BDAT message body handling when a client sends a TLS close_notify alert before the body transfer is complete, and then follows up with a final byte in cleartext on the same TCP connection,\u00bb Exim <a href=\"https:\/\/www.exim.org\/static\/doc\/security\/EXIM-Security-2026-05-01.1\/EXIM-Security-2026-05-01.1.txt\">said<\/a> in an advisory released today.<\/p>\n<div class=\"dog_two clear\">\n<div class=\"cf\"><a href=\"https:\/\/thehackernews.uk\/ai-cant-stop-d\" rel=\"nofollow noopener sponsored\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" class=\"lazyload\" alt=\"Cybersecurity\" src=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjPEV6-530TOlxG6PjrmdlY623wpBwduZ7t1HV6flcmO5R4q4AmfixDUzW0CrhlvMVNWbhvOIso-UDNTka4W_W9Chrdj_dglwBZwi7DuePM2IMIl-hfUYVIqBXgfpr_2619K8Gptb4LzwJ6gUbi7lWl2M8AFQJsHEaw63Q7tZ6708YGruiHrr0Y2W9YYxLQ\/s728-e100\/ThreatLocker-d.png\" width=\"729\" height=\"91\"\/><\/a><\/div>\n<\/div>\n<p>\u00abThis sequence of events can cause Exim to write into a memory buffer that has already been freed during the TLS session teardown, leading to heap corruption. An attacker only needs to be able to establish a TLS connection and use the CHUNKING (BDAT) SMTP extension.\u00bb<\/p>\n<p>The issue impacts all Exim versions from 4.97 up to and including 4.99.2. That said, it only affects builds that use USE_GNUTLS=yes, meaning builds that rely on other TLS libraries like OpenSSL are not impacted.<\/p>\n<p>Federico Kirschbaum, head of Security Lab at XBOW, an autonomous cybersecurity testing platform, has been credited with discovering and reporting the flaw on May 1, 2026.<\/p>\n<p>\u00abDuring TLS shutdown, Exim frees its TLS transfer buffer \u2013 but a nested BDAT receive wrapper can still process incoming bytes and end up calling ungetc(), which writes a single character (\\n) into the freed region,\u00bb Kirschbaum <a href=\"https:\/\/xbow.com\/blog\/dead-letter-cve-2026-45185-xbow-found-rce-exim\">said<\/a>. \u00abThat one-byte write lands on Exim&#8217;s allocator metadata, corrupting the allocator&#8217;s internal shape; the exploit then leverages that corruption to gain further primitives.\u00bb<\/p>\n<p><iframe loading=\"lazy\" title=\"BLOG Dead.Letter (CVE-2026-45185) How XBOW found an unauthenticated RCE on Exim - ASLR BYPASS\" width=\"500\" height=\"375\" src=\"https:\/\/www.youtube.com\/embed\/qHYr7Fb0JuI?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/p>\n<p>XBOW described the vulnerability as \u00abone of the highest-caliber bugs\u00bb discovered in Exim to date, adding that triggering it requires almost no special configuration on the server.<\/p>\n<p>The shortcoming has been addressed in version 4.99.3. All users are advised to upgrade as soon as possible. There are no mitigations that resolve the vulnerability.<\/p>\n<p>\u00abThe fix ensures that the input processing stack is cleanly reset when a TLS close notification is received during an active BDAT transfer, preventing the stale pointers from being used,\u00bb Exim noted.<\/p>\n<p>This is not the first time critical use-after-free bugs in Exim have been disclosed. In late 2017, Exim patched a use-after-free vulnerability in the SMTP daemon (<a href=\"https:\/\/devco.re\/blog\/2017\/12\/11\/Exim-RCE-advisory-CVE-2017-16943-en\/\">CVE-2017-16943<\/a>, CVSS score: 9.8) that unauthenticated attackers could have exploited to achieve remote code execution via specially crafted BDAT commands and seize control of the email server.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>\ue804Ravie Lakshmanan\ue802May 12, 2026Vulnerability \/ Email Security Exim has released security updates to address a severe security issue affecting certain configurations that could enable memory corruption and potential code execution.&hellip;<\/p>\n","protected":false},"author":1,"featured_media":896,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[1639,1641,10,13,1638,985,1640,1533,68],"class_list":["post-895","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-bdat","tag-builds","tag-code","tag-execution","tag-exim","tag-exposes","tag-gnutls","tag-potential","tag-vulnerability"],"_links":{"self":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts\/895","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=895"}],"version-history":[{"count":0,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts\/895\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/media\/896"}],"wp:attachment":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=895"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=895"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}