On this page (7 sections)

Ubuntu has published USN-9013-1, a security notice covering three vulnerabilities in Fetchmail, the long-standing tool that pulls mail from remote POP3 and IMAP servers and hands it to a local mail system. The most serious is a stack-based buffer overflow in builds with NTLM support, tracked as CVE-2026-94184.

If you run Fetchmail on a mail relay, a hosting server, a backup mailbox collector or a cron job that fetches mail for a website or application, this is worth a few minutes. Most of the impact is a crash that stalls inbound mail, but the NTLM issue could in theory lead to code execution.

What the Ubuntu notice covers

USN-9013-1 bundles three separate Fetchmail issues. They are old and new: one dates from 2021, one from October 2025 and one from September 2026. All three involve Fetchmail mishandling data sent by a mail server, which is the key point for assessing your risk.

The three issues in USN-9013-1
CVEWhat goes wrongLikely impactScore
CVE-2026-94184Stack buffer overflow while building an NTLM response (NTLM builds only)Crash, or possibly code execution8.1 High (GitHub); 5.3 (CVE record)
CVE-2025-61962SMTP client crashes on a 334 status code in a malformed contextDenial of service5.9 Medium
CVE-2021-36386Uninitialized va_list when logging long messagesCrash or garbage in logs7.5 High (GitHub)

Technical details

CVE-2026-94184: NTLM stack overflow

According to the GitHub advisory, a malicious or compromised mail server that advertises NTLM authentication can send a crafted Type 2 challenge. Fetchmail then writes past a fixed-size stack buffer while building its NTLM authenticate response. The advisory says this may lead to remote code execution depending on stack-frame layout, or to authentication failure or process termination when memory hardening is active. The weakness class is CWE-121, a classic stack overflow.

Ubuntu's notice credits the discovery to Tristan Madani and adds that the default compiler options for affected releases should reduce the vulnerability to a denial of service. That is Ubuntu's assessment of its own builds, not a guarantee for other distributions or custom builds. The issue only applies when Fetchmail was built with NTLM support and the server offers NTLM.

The two scores disagree. The GitHub advisory gives 8.1 (high, with high confidentiality, integrity and availability impact and high attack complexity), while the CVE record in the research lists 5.3 (medium). Treat the gap as unresolved and plan around the worse case.

CVE-2025-61962: SMTP authentication crash

The GitHub advisory states that in Fetchmail before 6.5.6, the SMTP client can crash when authenticating after receiving a 334 status code in a malformed context. Ubuntu describes the trigger as an attacker controlling a malicious server, with denial of service as the result.

CVE-2021-36386: long log messages

The Fetchmail project's security announcement explains that when Fetchmail assembles a long log or error message, it fails to reinitialize a variable argument list before reuse. Depending on platform and verbosity, the result ranges from nothing, to a garbled log line that could disclose information, to a segmentation fault that stops inbound mail. The project rates the danger as low, and the CVE text notes it is unclear whether any realistic platform sees more than an inconvenience.

Per the project, the first fix in 6.4.20 introduced a regression that truncates buffered log output (for example with --logfile). Release 6.4.21 and newer are listed as not affected. Ubuntu packages may backport fixes, so check your distribution's package notes rather than relying on the upstream number alone.

Who is realistically exposed

All three flaws require Fetchmail to talk to a hostile or compromised server, so the exposure depends on what you point it at.

  • Higher risk: Fetchmail polling third-party or shared mail providers, or servers you do not administer, over networks where an attacker could impersonate or tamper with the server.
  • Higher risk for CVE-2026-94184: setups that allow NTLM authentication and use a Fetchmail build with NTLM support.
  • Lower risk: Fetchmail fetching only from a mail server you fully control, using verified TLS.
  • Not affected: systems that do not have Fetchmail installed.

Websites tend to touch Fetchmail indirectly: a support inbox, a form-to-mail pipeline, or a legacy server that collects mail from an old ISP account. These are easy to forget, so inventory them.

How to check if you are exposed

First, see whether Fetchmail is installed and which version. This is read-only. On Debian and Ubuntu, the following lists the installed package and version:

Check the installed Fetchmail package and version (Debian/Ubuntu)Shell
dpkg -l fetchmail
fetchmail --version

The output shows the package version and whether the binary mentions NTLM among its compiled-in features. Next, look for configuration that actually uses NTLM, which tells you whether CVE-2026-94184 is reachable for you:

Search Fetchmail configuration for NTLM use (run as the user that owns the config)Shell
grep -i ntlm ~/.fetchmailrc /etc/fetchmailrc 2>/dev/null

No output means NTLM is not explicitly configured in those files, although a server may still negotiate it if authentication is left on automatic. Also check whether a systemd unit or cron entry runs Fetchmail, so you know what to restart after updating.

What to do now

  1. Find every host that runs Fetchmail, including old servers and containers.
  2. Compare the installed version with the fixed package listed in USN-9013-1 for your Ubuntu release.
  3. Update the package using your normal patch process (command below).
  4. Restart any long-running Fetchmail daemon so the new binary is loaded.
  5. Until patched, avoid NTLM authentication and fetch only from servers you trust, over verified TLS.
  6. Review logs for repeated Fetchmail crashes or unexplained stalls in inbound mail.
  7. Remove Fetchmail entirely where it is no longer needed.

This command refreshes package lists and upgrades only the Fetchmail package on Ubuntu:

Update only the Fetchmail package (Ubuntu)Shell
sudo apt update
sudo apt install --only-upgrade fetchmail
Caution. Restarting Fetchmail briefly pauses mail retrieval. If you run it as a daemon, restart it in a quiet period and confirm afterwards that mail is flowing again.

If Fetchmail runs as a systemd service, restart it and check its state. Adjust the unit name if yours differs:

Restart and verify the Fetchmail service (systemd)Shell
sudo systemctl restart fetchmail
systemctl status fetchmail

The status output should show the service active with a recent start time. The research does not list the exact fixed package versions per Ubuntu release, so take those from the Ubuntu notice itself. On other distributions, follow their own advisories; Red Hat has published errata for CVE-2026-94184, for example RHSA-2026:85959.

Detection and monitoring afterwards

A Fetchmail crash tends to look like mail silently stopping. Watch for the process exiting, segmentation fault messages in the system log, and gaps in expected mail volume. Also review authentication failures against your upstream mail servers, since the NTLM issue can show up as failed authentication when memory hardening stops the overflow.

Because these flaws depend on the remote server's behavior, keep the mail servers you fetch from under the same scrutiny: monitor their TLS certificates and DNS for unexpected changes. Webforta Monitor can watch certificate and DNS changes, and the free SSL checker gives a quick view of a server's certificate. For wider hygiene on servers that handle mail and web traffic, see our small business website security guide.

Exploitation status and open questions

The research does not report any active exploitation of these three CVEs, and none is listed in CISA's Known Exploited Vulnerabilities catalog. EPSS estimates in the GitHub advisories are low (for example 1.195% for CVE-2026-94184), though EPSS is only a probability estimate. Some details remain open: the exact fixed versions per release are in the Ubuntu notice rather than the CVE records, and the two severity scores for CVE-2026-94184 disagree.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2021-36386 - GitHub Advisory Databasegithub.com
  2. oss-security - ANNOUNCE: fetchmail <= 6.4.19 security announcement 2021-01 (CVE-2021-36386) - fetchmail 6.4.20 released. DoS or information disclosure in some configurationsopenwall.com
  3. https://www.fetchmail.info/fetchmail-SA-2021-01.txtfetchmail.info
  4. CVE-2025-61962 - GitHub Advisory Databasegithub.com
  5. CVE-2026-94184 - GitHub Advisory Databasegithub.com
  6. USN-9013-1: Fetchmail vulnerabilitiesubuntu.com ·
  • Fetchmail
  • Ubuntu
  • USN
  • NTLM
  • buffer overflow
  • email