How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

328,411

Total vulnerabilities in the database

Vulnerabilities for products matching "mailman"

Found 5 matching products. Filters apply to all results.

You can search for specific versions with /product/mailman/1.2.3

gnu / mailman

47 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-43921	Medium	April 20, 2025 4/20/25	>= 2.1.1 <= 2.1.39
CVE-2025-43920	Medium	April 20, 2025 4/20/25	>= 2.1.1 <= 2.1.39
CVE-2025-43919	Medium	April 20, 2025 4/20/25	>= 2.1.1 <= 2.1.39
CVE-2021-34337	Medium	April 15, 2023 4/15/23	< 3.3.5
CVE-2021-44227	High	December 2, 2021 12/2/21	< 2.1.38
CVE-2021-43331	Medium	November 12, 2021 11/12/21	< 2.1.36
CVE-2021-43332	Medium	November 12, 2021 11/12/21	< 2.1.36
CVE-2021-42096	Low	October 21, 2021 10/21/21	< 2.1.35
CVE-2021-42097	High	October 21, 2021 10/21/21	< 2.1.35
CVE-2020-15011	Low	June 24, 2020 6/24/20	< 2.1.33
CVE-2020-12108	Medium	May 6, 2020 5/6/20	< 2.1.31
CVE-2020-12137	Medium	April 24, 2020 4/24/20	>= 2.0 < 2.1.30
CVE-2018-0618	Low	July 26, 2018 7/26/18	<= 2.1.26
CVE-2018-13796	Low	July 12, 2018 7/12/18	< 2.1.28
CVE-2018-5950	Medium	January 23, 2018 1/23/18	< 2.1.26
CVE-2016-7123	Medium	September 2, 2016 9/2/16	<= 2.1.14
CVE-2016-6893	Medium	September 2, 2016 9/2/16	== 2.1.13 == 2.1.5 == 2.1.21 == 2.1.11-rc1 == 2.1.19-rc1 == 2.1.21-rc2 == 2.1.3 == 2.1.16 == 2.1.18 == 2.1.10b1 == 2.1.8 == 2.1.11-rc2 == 2.1.15 == 2.1.23 == 2.1.19 == 2.1.13-rc1 == 2.1.11 == 2.1.22 == 2.1.2 == 2.1.18-rc1 == 2.1.9 == 2.1.18-1 == 2.1.14-rc1 == 2.1.10b3 == 2.1.19-rc3 == 2.1.6 == 2.1.18-rc2 == 2.1 == 2.1.18-rc3 == 2.1.10-rc1 == 2.1.14-1 == 2.1.20 == 2.1.12-rc2 == 2.1.16-rc1 == 2.1.15-rc1 == 2.1.16-rc2 == 2.1.14 == 2.1.16-rc3 == 2.1.10 == 2.1.1 == 2.1.12 == 2.1.4 == 2.1.12-rc1 == 2.1.10b4 == 2.1.17 == 2.1.19-rc2
CVE-2015-2775	High	April 13, 2015 4/13/15	<= 2.1.19
CVE-2011-5024	Low	December 29, 2011 12/29/11	== 2.1.3 == 2.1.8 == 2.1.11 == 2.1.2 == 2.1.9 == 2.0.13 == 2.1.6 == 2.1 == 2.1.10 == 2.1.1 == 2.1.12 == 2.1.7 == 2.1.4
CVE-2011-0707	Low	February 22, 2011 2/22/11	== 2.1.13 == 2.1.5 == 2.1.11-rc1 == 2.0.5 == 2.0.1 == 2.1.5.8 == 2.1.3 == 2.0.11 == 2.0.6 == 2.0-beta3 == 2.1.8 == 2.1.11-rc2 == 1.1 == 2.0.14 == 2.0-beta5 == 2.0.12 == 2.1.13-rc1 == 2.0 == 2.1.11 == 2.0-beta4 == 2.1.2 == 2.0.9 == 2.1.9 == 2.0.3 == 2.1-stable == 2.1.14-rc1 == 2.0.13 == 2.1.6 == 2.1-alpha == 2.0.4 == 2.1 == 2.1-beta == 2.1b1 <= 2.1.14 == 2.1.10 == 2.1.1 == 2.1.12 == 1.0 == 2.0.8 == 2.1.7 == 2.1.4 == 2.0.10 == 2.1.1-beta1 == 2.0.2 == 2.0.7
CVE-2010-3089	Low	September 15, 2010 9/15/10	== 2.1.5 == 2.1.11-rc1 == 2.1.3 == 2.1.8 == 2.1.11-rc2 == 2.1.13-rc1 == 2.1.11 == 2.1.2 == 2.1.9 == 2.1-stable == 2.1.6 == 2.1-alpha == 2.1 <= 2.1.13 == 2.1-beta == 2.1.10 == 2.1.1 == 2.1.12 == 2.1.7 == 2.1.4
CVE-2006-2191	High	September 19, 2006 9/19/06	<= 2.1.8
CVE-2006-4624	Low	September 7, 2006 9/7/06	<= 2.1.8
CVE-2006-2941	Medium	September 6, 2006 9/6/06	== 2.1.5 == 2.1.5.8 == 2.1.3 == 2.1.8 == 2.1.2 == 2.1.6 == 2.1 == 2.1b1 == 2.1.1 == 2.1.7 == 2.1.4 == 2.1.1-beta1
CVE-2006-3636	Medium	September 6, 2006 9/6/06	== 2.1.5 == 2.1.5.8 == 2.1.3 == 2.1.8 == 2.1.2 == 2.1.6 == 2.1 == 2.1b1 == 2.1.1 == 2.1.7 == 2.1.4 == 2.1.1-beta1
CVE-2006-1712	Low	April 11, 2006 4/11/06	== 2.1.7
CVE-2006-0052	Medium	March 31, 2006 3/31/06	== 2.1.5 == 2.0.5 == 2.0.1 == 2.1.3 == 2.0.11 == 2.0.6 == 2.0-beta3 == 1.1 == 2.0.14 == 2.0-beta5 == 2.0.12 == 2.0 == 2.0-beta4 == 2.1.2 == 2.0.9 == 2.0.3 == 2.0.13 == 2.0.4 == 2.1 == 2.1b1 == 2.1.1 == 1.0 == 2.0.8 == 2.1.4 == 2.0.10 == 2.0.2 == 2.0.7
CVE-2005-4153	High	December 11, 2005 12/11/05	== 2.1.5 == 2.1.6 == 2.1.4
CVE-2005-3573	Medium	November 16, 2005 11/16/05	== 2.1.5 == 2.0.5 == 2.0.1 == 2.1.5.8 == 2.1.3 == 2.0.11 == 2.0.6 == 2.0-beta3 == 2.0.14 == 2.0-beta5 == 2.0.12 == 2.0-beta4 == 2.1.2 == 2.0.9 == 2.0.3 == 2.0.13 == 2.0.4 == 2.1 == 2.0.8 == 2.1.4 == 2.0.10 == 2.1.1-beta1 == 2.0.2 == 2.0.7
CVE-2005-0080	Medium	May 2, 2005 5/2/05	== 2.1.5
CVE-2005-0202	Medium	May 2, 2005 5/2/05	== 2.1.5 == 2.1.3 == 2.1.2 == 2.1 == 2.1b1 == 2.1.1 == 2.1.4
CVE-2004-1177	Low	January 10, 2005 1/10/05	== 2.0.5 == 2.0.1 == 2.1.3 == 2.0.11 == 2.0.6 == 2.0-beta3 == 1.1 == 2.0-beta5 == 2.0.12 == 2.0 == 2.0-beta4 == 2.1.2 == 2.0.9 == 2.0.3 == 2.0.13 == 2.0.4 == 2.1 == 2.1b1 == 2.1.1 == 1.0 == 2.0.8 == 2.1.4 == 2.0.10 == 2.0.2 == 2.0.7
CVE-2004-1143	High	December 31, 2004 12/31/04	== 2.0.5 == 2.0.1 == 2.1.3 == 2.0.11 == 2.0.6 == 2.0-beta3 == 1.1 == 2.0-beta5 == 2.0.12 == 2.0 == 2.0-beta4 == 2.1.2 == 2.0.9 == 2.0.3 == 2.0.13 == 2.0.4 == 2.1 == 2.1b1 == 2.1.1 == 1.0 == 2.0.8 == 2.1.4 == 2.0.10 == 2.0.2 == 2.0.7
CVE-2004-0412	Medium	August 18, 2004 8/18/04	== 2.1.3 == 2.1.2 == 2.1 == 2.1b1 == 2.1.1 == 2.1.4
CVE-2004-0182	Medium	June 1, 2004 6/1/04	<= 2.0.12
CVE-2003-0991	Medium	March 3, 2004 3/3/04	== 2.0.5 == 2.0.1 == 2.0.11 == 2.0.6 == 2.0-beta3 == 1.1 == 2.0-beta5 == 2.0.12 == 2.0 == 1.0 == 2.0.13 == 2.0.2 == 2.0.3 == 2.0-beta4 == 2.0.4 == 2.0.8 == 2.0.9 == 2.1 == 2.0.10 == 2.0.7
CVE-2003-0965	Medium	February 17, 2004 2/17/04	<= 2.1.4
CVE-2003-0992	Low	February 17, 2004 2/17/04	<= 2.1.3
CVE-2003-0038	Low	February 7, 2003 2/7/03	== 2.1
CVE-2002-0855	High	September 5, 2002 9/5/02	== 2.0.12
CVE-2002-0388	High	June 18, 2002 6/18/02	<= 2.0.11
CVE-2002-0389	Low	June 18, 2002 6/18/02	*
CVE-2001-0884	Medium	December 21, 2001 12/21/01	== 5.0 * == 7.0 == 5.1 == 6.0
CVE-2001-1132	High	September 5, 2001 9/5/01	<= 2.0.5
CVE-2001-0290	Low	May 3, 2001 5/3/01	<= 2.0.2
CVE-2000-0861	High	November 14, 2000 11/14/00	== 1.1
CVE-2000-0701	Low	October 20, 2000 10/20/00	== 2.0-beta3 == 2.0-beta4

mailman / mailman

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2008-0564	Low		February 5, 2008 2/5/08	<= 2.1.10b

kjtechforce / mailman

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2009-2164	Medium		June 22, 2009 6/22/09	== beta1

suse / mailman

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2019-3693	High		January 24, 2020 1/24/20	< 2.1.15-9.6.15.1 < 2.1.17-3.11.1 <= 2.1.29-lp151.2.14

mailman

3 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-34337	Medium	April 15, 2023 4/15/23	< 3.3.5
CVE-2021-44227	High	December 2, 2021 12/2/21	< 2.1.38
CVE-2018-13796	Low	July 12, 2018 7/12/18	< 2.1.28

Showing vulnerabilities for 5 products matching "mailman". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.