CVE-2021-42097
Description
GNU Mailman before 2.1.35 allows CSRF token reuse across user sessions, enabling a list member to perform account takeover of another member via CSRF.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
GNU Mailman before 2.1.35 allows CSRF token reuse across user sessions, enabling a list member to perform account takeover of another member via CSRF.
Vulnerability
GNU Mailman versions prior to 2.1.35 contain a cross-site request forgery (CSRF) vulnerability in the user options page. The csrf_token value is not bound to a specific user session; a token generated for one user can be reused by another. This allows an authenticated list member to obtain a valid token from their own session and use it to craft a CSRF attack against another list member. The vulnerability affects all Mailman 2.1.x releases before 2.1.35 [1][2][3].
Exploitation
An attacker must be a member of the target mailing list. The attacker first obtains a csrf_token from their own session (e.g., by visiting the user options page). They then engineer a victim (another list member with an active session) to submit a crafted request containing that token, typically via a malicious link or email. Because the token is not user-specific, the server accepts it and executes the attacker's intended actions under the victim's authentication context [2].
Impact
Successful exploitation allows the attacker to perform any action the victim can perform on the Mailman web interface, including changing the victim's password, email address, or other account settings. This effectively results in account takeover. The attack is limited to list members; non-members cannot initiate it [1][3].
Mitigation
The vulnerability is fixed in Mailman 2.1.35, released on October 19, 2021 [1][3]. Users are advised to upgrade immediately. For those unable to upgrade, a patch is available from the Mailman project [1]. No other workarounds are documented.
AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
5- GNU/Mailmandescription
- osv-coords3 versionspkg:rpm/almalinux/mailmanpkg:rpm/opensuse/mailman&distro=openSUSE%20Leap%2015.2pkg:rpm/suse/mailman&distro=SUSE%20Package%20Hub%2015%20SP2
< 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2+ 2 more
- (no CPE)range: < 3:2.1.29-12.module_el8.5.0+26+48d4c9ee.2
- (no CPE)range: < 2.1.35-lp152.7.6.1
- (no CPE)range: < 2.1.35-bp152.7.6.1
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
4- www.debian.org/security/2021/dsa-4991mitrevendor-advisoryx_refsource_DEBIAN
- www.openwall.com/lists/oss-security/2021/10/21/4mitremailing-listx_refsource_MLIST
- bugs.launchpad.net/mailman/+bug/1947640mitrex_refsource_CONFIRM
- mail.python.org/archives/list/mailman-announce%40python.org/thread/IKCO6JU755AP5G5TKMBJL6IEZQTTNPDQ/mitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.