Important: mailman:2.1 security update

mailman Updated 02 Oct 2025

Summary

02/12/2021
N/A
Yes i
Unrated
Not published

ALSA-2021:4916: Important: mailman:2.1 security update. Affects mailman across 2 version ranges.

< 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2 < 3:2.1.29-12.module_el8.5.0+2602+327eb9f3.2

Fixed in 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2 or 3:2.1.29-12.module_el8.5.0+2602+327eb9f3.2, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Mailman is a program used to help manage e-mail discussion lists. It provides a range of features for list administrators and subscribers, including list creation, moderation, archiving, and more. This vulnerability affects the Mailman version 2.1.

Vulnerability Detail

The vulnerability identified as CVE-2021-44227 is a Cross-Site Request Forgery (CSRF) token bypass issue in Mailman. This vulnerability allows an attacker to perform CSRF attacks and potentially take over the admin privileges. CSRF attacks can lead to unauthorized actions being performed on behalf of the victim, compromising the security and integrity of the system. The impact of this vulnerability can be severe, as it enables an attacker to gain control over the Mailman administration and potentially manipulate mailing lists, send malicious emails, or access sensitive information.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

sudo dnf update mailman
  • < 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2
  • < 3:2.1.29-12.module_el8.5.0+2602+327eb9f3.2 3:2.1.29-12.module_el8.5.0+2602+327eb9f3.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. It is crucial to apply the recommended fix by updating Mailman to the latest version as soon as possible.

Conclusion

The identified vulnerability in Mailman version 2.1 (CVE-2021-44227) poses a significant security risk, allowing for CSRF attacks and potential admin takeover. To mitigate this risk, it is crucial to update Mailman to version 2.1.29-12.module_el8.5.0+26+48d4c9ee.2 or later. This update includes the necessary security patches and enhancements to prevent CSRF token bypass. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for mailman →

Share this vulnerability

FAQ

Mailman is a program used for managing e-mail discussion lists. It provides various features for list administrators and subscribers, facilitating efficient communication and collaboration.

A CSRF token bypass vulnerability allows an attacker to bypass the CSRF protection mechanisms in a web application. This can enable them to perform unauthorized actions on behalf of a victim user, potentially leading to account compromise or other security issues.

The impact of this vulnerability is significant as it allows an attacker to perform CSRF attacks and potentially take over the admin privileges in Mailman. This can lead to unauthorized manipulation of mailing lists, sending of malicious emails, and access to sensitive information.

To fix this vulnerability, update Mailman to version 2.1.29-12.module_el8.5.0+26+48d4c9ee.2 or later. This update includes the necessary security patches and improvements to prevent CSRF token bypass attacks.

No specific workaround is mentioned for this vulnerability. It is essential to apply the recommended fix by updating Mailman to the latest version.

Related vulnerabilities

Recent vulnerabilities recorded for mailman.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

sudo dnf update mailman
  • < 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2
  • < 3:2.1.29-12.module_el8.5.0+2602+327eb9f3.2 3:2.1.29-12.module_el8.5.0+2602+327eb9f3.2

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback