Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

haproxy

About This Vendor

haproxy is a technology vendor producing software and infrastructure products. As a software provider, haproxy's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of haproxy's products are critical for organizations running their software in production environments.

Vulnerability Trends for This Vendor

SecUtils has indexed 32 known vulnerabilities from haproxy. This includes 2 critical-severity issues and 20 high-severity issues that represent significant risk. These vulnerabilities affect 28 distinct products across haproxy's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2012 through 2025, indicating decades of continuous security attention and research. Organizations deploying haproxy products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.

ID Date Published Last Modified Severity (CVSSv3) Severity (CVSSv2) Exploit Available
CVE-2012-2942 2012-05-27 2025-04-11 - 5.1 Unknown
CVE-2013-1912 2013-04-10 2025-04-11 - 5.1 Unknown
CVE-2013-2175 2013-08-19 2025-04-11 - 5.0 Likely
CVE-2014-6269 2014-09-30 2025-04-12 - 5.0 Likely
CVE-2015-3281 2015-07-06 2025-04-12 - 5.0 Likely
CVE-2016-5360 2016-06-30 2025-04-12 7.5 5.0 Likely
CVE-2016-2102 2017-08-22 2025-04-20 5.3 5.0 Likely
CVE-2018-10184 2018-05-09 2024-11-21 7.5 5.0 Likely
CVE-2018-11469 2018-05-25 2024-11-21 5.9 4.3 Likely
CVE-2018-14645 2018-09-21 2024-11-21 7.5 5.0 Likely
CVE-2018-20102 2018-12-12 2024-11-21 7.5 5.0 Likely
CVE-2018-20103 2018-12-12 2024-11-21 7.5 5.0 Likely
CVE-2018-20615 2019-03-21 2024-11-21 7.5 5.0 Likely
CVE-2019-11323 2019-05-09 2024-11-21 5.9 4.3 Likely
CVE-2019-14241 2019-07-23 2024-11-21 7.5 5.0 Likely
CVE-2019-14243 2019-07-23 2024-11-21 7.5 5.0 Likely
CVE-2019-18277 2019-10-23 2024-11-21 7.5 4.3 Likely
CVE-2019-19330 2019-11-27 2024-11-21 9.8 7.5 Likely
CVE-2020-11100 2020-04-02 2024-11-21 8.8 6.5 Likely
CVE-2021-39240 2021-08-17 2024-11-21 7.5 5.0 Likely
CVE-2021-39241 2021-08-17 2024-11-21 5.3 5.0 Likely
CVE-2021-39242 2021-08-17 2024-11-21 7.5 5.0 Likely
CVE-2021-40346 2021-09-08 2024-11-21 7.5 5.0 Likely
CVE-2022-0711 2022-03-02 2024-11-21 7.5 5.0 Likely
CVE-2023-25725 2023-02-14 2025-03-20 9.1 - -
CVE-2023-0056 2023-03-23 2025-02-25 6.5 - -
CVE-2023-0836 2023-03-29 2025-02-18 7.5 - -
CVE-2023-25950 2023-04-11 2025-02-11 7.3 - -
CVE-2023-40225 2023-08-10 2024-11-21 7.2 - -
CVE-2023-45539 2023-11-28 2024-11-21 8.2 - -
CVE-2024-45506 2024-09-04 2025-03-14 7.5 - -
CVE-2025-11230 2025-11-19 2025-12-19 7.5 - -

How SecUtils Normalizes Vendor Data

SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for haproxy by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with haproxy's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.