<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T04:56:48.002539+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2021-32749</id>
    <title>CVE-2021-32749 — Possible RCE vulnerability in mailing action using mailutils (mail-whois)</title>
    <updated>2026-10-07T04:56:48.005510+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> fail2ban</p>
<p>fail2ban is a daemon to ban hosts that cause multiple authentication errors. In versions 0.9.7 and prior, 0.10.0 through 0.10.6, and 0.11.0 through 0.11.2, there is a vulnerability that leads to possible remote code execution in the mailing action mail-whois. Command `mail` from mailutils package used in mail actions like `mail-whois` can execute command if unescaped sequences (`\n~`) are available in "foreign" input (for instance in whois output). To exploit the vulnerability, an attacker would need to insert malicious characters into the response sent by the whois server, either via a MITM attack or by taking over a whois server. The issue is patched in versions 0.10.7 and 0.11.3. As a workaround, one may avoid the usage of action `mail-whois` or patch the vulnerability manually.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2021-32749"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-5232-1</id>
    <title>USN-5232-1 — fail2ban vulnerability</title>
    <updated>2026-10-07T04:56:48.005625+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: fail2ban, Ubuntu:Pro:16.04:LTS: fail2ban, Ubuntu:Pro:18.04:LTS: fail2ban, Ubuntu:Pro:20.04:LTS: fail2ban</p>
<p>Jakub Żoczek discovered that certain Fail2ban actions handled whois responses in
an insecure way. If Fail2ban was configured to use certain mail actions
like 'mail-whois' on a target system, a remote attacker who was able to control whois
responses to this target system could possibly execute arbitrary code.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-5232-1"/>
  </entry>
</feed>
