Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11230: CWE-407 Inefficient Algorithmic Complexity in HAProxy Technologies HAProxy Community Edition

1
High
VulnerabilityCVE-2025-11230cvecve-2025-11230cwe-407
Published: Wed Nov 19 2025 (11/19/2025, 09:28:39 UTC)
Source: CVE Database V5
Vendor/Project: HAProxy Technologies
Product: HAProxy Community Edition

Description

Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to cause a denial of service via specially crafted JSON requests.

AI-Powered Analysis

AILast updated: 11/19/2025, 09:56:33 UTC

Technical Analysis

CVE-2025-11230 identifies a vulnerability in HAProxy Community Edition related to inefficient algorithmic complexity within the mjson JSON parsing library. Specifically, the vulnerability arises because the JSON parser does not efficiently handle certain crafted JSON inputs, leading to excessive computational resource consumption. This inefficiency can be exploited remotely by attackers who send specially crafted JSON requests to HAProxy instances, causing the service to consume excessive CPU or memory resources, ultimately resulting in a denial of service (DoS) condition. The vulnerability affects multiple versions of HAProxy Community Edition, from 2.4.0 through 3.2.0, indicating a broad impact across recent releases. The CVSS 3.1 base score of 7.5 reflects a high severity rating, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), no impact on confidentiality or integrity (C:N/I:N), but high impact on availability (A:H). No patches were listed at the time of publication, and no known exploits have been observed in the wild, but the vulnerability's characteristics suggest it could be weaponized for DoS attacks against HAProxy deployments. HAProxy is widely used as a high-performance TCP/HTTP load balancer and proxy, often deployed in front of web applications and APIs, making this vulnerability particularly relevant for internet-facing infrastructure.

Potential Impact

For European organizations, the primary impact of CVE-2025-11230 is the potential for denial of service attacks that can disrupt critical web services and applications relying on HAProxy for load balancing and proxy functions. This can lead to service outages, degraded user experience, and potential financial losses, especially for sectors such as finance, e-commerce, telecommunications, and public services that depend on high availability. The vulnerability does not compromise confidentiality or integrity directly but threatens availability, which can indirectly affect business continuity and trust. Organizations with large-scale or high-traffic HAProxy deployments are at greater risk, as attackers can exploit the inefficient JSON parsing to exhaust server resources rapidly. Additionally, the lack of required authentication and user interaction lowers the barrier for attackers, increasing the likelihood of exploitation attempts. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as public knowledge of the vulnerability grows.

Mitigation Recommendations

To mitigate CVE-2025-11230, European organizations should prioritize the following actions: 1) Monitor HAProxy vendor communications closely and apply official patches or updates as soon as they become available to address the inefficient algorithmic complexity in mjson. 2) Implement network-level rate limiting and filtering to restrict the volume and frequency of JSON requests reaching HAProxy instances, reducing the risk of resource exhaustion. 3) Deploy Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with rules designed to detect and block anomalous or malformed JSON payloads that could trigger the vulnerability. 4) Conduct regular performance and resource usage monitoring on HAProxy servers to detect unusual spikes indicative of exploitation attempts. 5) Where feasible, isolate HAProxy instances behind additional proxy layers or use containerization to limit the impact of potential DoS attacks. 6) Review and harden JSON input validation in upstream applications to reduce reliance on HAProxy for filtering malformed requests. 7) Educate security and operations teams about the vulnerability and signs of exploitation to enable rapid response. These measures go beyond generic advice by focusing on proactive detection, containment, and layered defense tailored to the nature of this algorithmic complexity vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
canonical
Date Reserved
2025-10-01T13:10:26.249Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691d90cc12537358e424faf3

Added to database: 11/19/2025, 9:41:32 AM

Last enriched: 11/19/2025, 9:56:33 AM

Last updated: 11/19/2025, 10:59:56 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats