New Exim BDAT Vulnerability Exposes GnuTLS Builds to Potential Code Execution

New Exim BDAT Vulnerability Exposes GnuTLS Builds to Potential Code Execution

New Exim BDAT Vulnerability Exposes GnuTLS Builds to Potential Code Execution

https://thehackernews.com/2026/05/new-exim-bdat-vulnerability-exposes.html

Publish Date: 2026-05-12 12:44:00

Source Domain: thehackernews.com

Ravie LakshmananMay 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.

Exim is an open-source Mail Transfer Agent (MTA) designed for Unix-like systems to receive, route, and deliver email.

The vulnerability, tracked as CVE-2026-45185, aka Dead.Letter, has been described as a use-after-free vulnerability in Exim’s binary data transmission (BDAT) message body parsing when a TLS connection is handled by GnuTLS.

“The 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,” Exim said in an advisory released today.

“This 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.”

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.

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.

“During TLS shutdown, Exim frees its TLS transfer buffer – 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,” Kirschbaum said. “That one-byte write lands on Exim’s allocator metadata, corrupting the allocator’s internal shape; the exploit then leverages that corruption to gain further primitives.”

XBOW described the vulnerability…

Source