# CVE-2025-11230: Denial of service vulnerability in HAProxy mjson library > Remote attackers can cause denial of service in HAProxy by sending specially crafted JSON requests due to inefficient algorithm complexity in the mjson library. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Nov 2025 - **Updated:** 19 Nov 2025 - **Also known as:** ALSA-2025:21691, ALSA-2025:21693, AZL-70538, AZL-70583, BIT-haproxy-2025-11230, CLSA-2025-1764324159, CLSA-2025-1765545936, DEBIAN-CVE-2025-11230, DSA-6017-1, GHSA-fc36-5gc3-jmhx, MGASA-2025-0242, MINI-44p7-c2xg-qgjq, MINI-4v3h-cv55-gvq7, MINI-h79v-4h69-2664, MINI-hwcv-3w9r-67pj, MINI-m7hv-7j3w-vp8j, MINI-r9v3-g76g-89f5, OESA-2025-2418, OESA-2025-2419, OESA-2025-2420, OESA-2025-2421, OESA-2025-2422, RHSA-2025:21691, RHSA-2025:21692, RHSA-2025:21693, RHSA-2025:21694, RHSA-2025:22398, RHSA-2025:22399, RHSA-2025:22422, RHSA-2026:8729, RLSA-2025:21691, RLSA-2025:21693, SUSE-SU-2025:03587-1, SUSE-SU-2025:03589-1, SUSE-SU-2025:20872-1, SUSE-SU-2025:20900-1, SUSE-SU-2026:20092-1, SUSE-SU-2026:20094-1, SUSE-SU-2026:20109-1, UBUNTU-CVE-2025-11230, USN-7805-1, openSUSE-SU-2025:15599-1, openSUSE-SU-2026:20032-1 ## What is CVE-2025-11230? CVE-2025-11230 is a high-severity denial of service vulnerability in HAProxy Community Edition, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Inefficient algorithm complexity in mjson in HAProxy allows remote attackers to cause a denial of service via specially crafted JSON requests. Weakness: CWE-407 (Inefficient Algorithmic Complexity) ## Which versions are affected by CVE-2025-11230? 1 open source package ship an affected version, including haproxy. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `haproxy` | Bitnami | From 2.4.0 | 2.4.30, 2.6.23, 2.8.16, 3.0.12, 3.1.9, 3.2.6 | | `haproxy` | AlmaLinux:10 | All versions | 3.0.5-4.el10_1.1 | | `haproxy` | AlmaLinux:9 | All versions | 2.8.14-1.el9_7.1 | | `haproxy` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.0.5-4.el10_1.1 | | `haproxy-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.0.5-4.el10_1.1 | | `haproxy-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.0.5-4.el10_1.1 | | `haproxy` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.8.14-1.el9_7.1 | | `haproxy-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.8.14-1.el9_7.1 | | `haproxy-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.8.14-1.el9_7.1 | | `haproxy` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.0.5-4.el10_0.1 | | `haproxy-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.0.5-4.el10_0.1 | | `haproxy-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.0.5-4.el10_0.1 | | `haproxy` | Red Hat:hummingbird:1 | All versions | 0:3.0.19-1.hum1 | | `haproxy` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.4.7-2.el9_0.3 | | `haproxy-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.4.7-2.el9_0.3 | | `haproxy-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.4.7-2.el9_0.3 | | `haproxy` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:2.4.17-6.el9_2.3 | | `haproxy-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:2.4.17-6.el9_2.3 | | `haproxy-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:2.4.17-6.el9_2.3 | | `haproxy` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:2.4.22-3.el9_4.1 | | `haproxy-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:2.4.22-3.el9_4.1 | | `haproxy-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:2.4.22-3.el9_4.1 | | `haproxy` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:2.4.22-4.el9_6.1 | | `haproxy-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:2.4.22-4.el9_6.1 | | `haproxy-debugsource` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:2.4.22-4.el9_6.1 | | `haproxy` | Rocky Linux:10 | All versions | 0:3.0.5-4.el10_1.1 | | `haproxy` | Rocky Linux:9 | All versions | 0:2.8.14-1.el9_7.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 2.4.22+git0.f8e3218e2-150400.3.25.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP5 | All versions | 2.4.22+git0.f8e3218e2-150400.3.25.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP6 | All versions | 2.8.11+git0.01c1056a4-150600.3.9.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP7 | All versions | 2.8.11+git0.01c1056a4-150600.3.9.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 16.0 | All versions | 3.2.0+git0.e134140d2-160000.3.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.4.22+git0.f8e3218e2-150400.3.25.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.4.22+git0.f8e3218e2-150400.3.25.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.4.22+git0.f8e3218e2-150400.3.25.1 | | `haproxy` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 3.2.0+git0.e134140d2-160000.3.1 | | `haproxy` | SUSE:Linux Micro 6.0 | All versions | 2.8.11+git0.01c1056a4-2.1 | | `haproxy` | SUSE:Linux Micro 6.1 | All versions | 2.8.11+git0.01c1056a4-slfo.1.1_2.1 | | `haproxy` | SUSE:Linux Micro 6.2 | All versions | 3.2.0+git0.e134140d2-160000.3.1 | | `haproxy` | openSUSE:Leap 15.6 | All versions | 2.8.11+git0.01c1056a4-150600.3.9.1 | Products: Haproxy Aloha Appliance, Haproxy Haproxy, Haproxy Haproxy Enterprise, Haproxy Kubernetes Ingress Controller. ## How do I fix CVE-2025-11230? Upgrade haproxy to a fixed version for your release line: 2.4.30, 2.6.23, 2.8.16 or 3.0.12. ## Is CVE-2025-11230 being exploited? There is no known exploitation of CVE-2025-11230 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-11230 and fix it if it is affected. What it is: CVE-2025-11230 is a high-severity denial of service vulnerability in HAProxy Community Edition, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-11230 in the wild and no public exploit code. Affected packages and fixed versions: - haproxy (Bitnami): affected from 2.4.0; fixed in 2.4.30, 2.6.23, 2.8.16, 3.0.12, 3.1.9, 3.2.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-11230/ (Markdown: https://insights.sbomify.com/CVE-2025-11230/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11230 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11230 - OSV: https://osv.dev/vulnerability/CVE-2025-11230 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-11230/ Summaries are generated and may contain mistakes; the official description above is the record.