dbcve.org
Aloha ApplianceApplication · Haproxy

CVE-2025-11230

HIGH · 7.5 CVSS v3.1 Published 2025-11-19
Fix available
A fix is available. Upgrade to 1.9.14-ee7 / 1.11.12-ee10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an algorithmic complexity vulnerability in the mjson JSON parsing library integrated into HAProxy. Specially crafted JSON requests with specific patterns (such as deeply nested structures or specially arranged tokens) cause the parser to consume CPU resources quadratically or worse, leading to denial of service. A remote attacker can exploit this without authentication by sending malicious JSON payloads.

MitigationUpdate HAProxy to the version containing the patched mjson library that addresses the inefficient algorithm. Implement request size limits and rate limiting on JSON-handling endpoints as a defensive measure until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aloha ApplianceApplication
Affected:>= 14.5.0, < 14.5.33>= 15.5.0, < 15.5.28>= 16.5.0, < 16.5.19>= 17.0.0, < 17.0.7
HaproxyWeb server / proxy
Affected:>= 2.4.0, < 2.4.30>= 2.6.0, < 2.6.23>= 2.8.0, < 2.8.16>= 3.0.0, < 3.0.12>= 3.1.0, < 3.1.9>= 3.2.0, < 3.2.6
Haproxy EnterpriseWeb server / proxy
Affected:= 2.4r1= 2.6r1= 2.8r1= 3.0r1= 3.1r1
Kubernetes Ingress ControllerApplication
Affected:< 1.9.14-ee7< 3.1.12>= 1.10.10-ee1, < 1.11.12-ee10>= 3.0.0-ee1, < 3.0.15-ee4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify HAProxy installed version
    Run 'haproxy -v' or check the package manager for version info (dpkg -l haproxy, rpm -qi haproxy, or docker image inspect)
    Affected if The installed version falls within any of these ranges: 2.4.0-2.4.29, 2.6.0-2.6.22, 2.8.0-2.8.15, 3.0.0-3.0.11, 3.1.0-3.1.8, 3.2.0-3.2.5, 14.5.0-14.5.32, 15.5.0-15.5.27, 16.5.0-16.5.18, 17.0.0-17.0.6, or specific Enterprise/KIC versions listed in the advisory
  2. Check if JSON parsing is enabled in HAProxy configuration
    Inspect HAProxy configuration files (typically /etc/haproxy/haproxy.cfg) and look for use of json or mjson in http-request rules, converters, or backend processing
    Affected if JSON parsing features (http-request set-var, use-backend with json, or any mjson-related configuration) are configured and exposed to untrusted input
  3. Identify product type for accurate version mapping
    Determine if running Aloha Appliance, HAProxy Enterprise, or Kubernetes Ingress Controller. For KIC, check the controller image version via 'kubectl get deployment -n ingress-controller' or container image inspect
    Affected if Running Kubernetes Ingress Controller with version < 1.9.14-ee7, < 3.1.12, >= 1.10.10-ee1 but < 1.11.12-ee10, or >= 3.0.0-ee1 but < 3.0.15-ee4; or running Enterprise releases 2.4r1, 2.6r1, 2.8r1, 3.0r1, or 3.1r1
  4. Verify exposed JSON-handling endpoints
    Review frontend and backend configurations for any routes or APIs that accept JSON payloads, check for http-request rules that process JSON body or headers
    Affected if Endpoints exist that accept and parse JSON input from clients without additional filtering
  5. Check mjson library version if accessible
    If the mjson library is bundled separately, inspect the library file version or check HAProxy build information for the embedded mjson version (may require examining binary or build logs)
    Affected if The embedded mjson library version is older than the patched version that addresses the algorithmic complexity flaw

You are affected if your installed HAProxy version falls within the vulnerable ranges AND your configuration exposes JSON parsing functionality to potentially untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.14-ee7 / 1.11.12-ee10 / 2.4.30 or later
Fixed in 1.9.14-ee71.11.12-ee102.4.30
Interim mitigation

Update HAProxy to the version containing the patched mjson library that addresses the inefficient algorithm. Implement request size limits and rate limiting on JSON-handling endpoints as a defensive measure until the patch is applied.

Recommended fix High confidence

HAProxy: 2.4.30 / 2.6.23 / 2.8.16 / 3.0.12 (choose based on your current branch); Aloha Appliance: 14.5.33 / 15.5.28 / 16.5.19 / 17.0.7; KIC: 1.9.14-ee7 / 3.1.12 / 1.11.12-ee10 / 3.0.15-ee4

  1. 1. Identify the current installed version of HAProxy, HAProxy Enterprise, Aloha Appliance, or Kubernetes Ingress Controller using 'haproxy -v' or checking the product documentation.
  2. 2. Based on your current major version line, determine the minimum fixed version required: For HAProxy 2.4.x upgrade to >=2.4.30; 2.6.x upgrade to >=2.6.23; 2.8.x upgrade to >=2.8.16; 3.0.x upgrade to >=3.0.12
  3. 3. For Aloha Appliance: 14.x upgrade to >=14.5.33; 15.x upgrade to >=15.5.28; 16.x upgrade to >=16.5.19; 17.x upgrade to >=17.0.7
  4. 4. For Kubernetes Ingress Controller: upgrade to >=1.9.14-ee7 (EE), >=3.1.12 (O), >=1.11.12-ee10 (EE 1.10+), or >=3.0.15-ee4 (EE 3.0+) as applicable
  5. 5. Review the HAProxy upgrade guide at https://www.haproxy.com/documentation for version-specific migration considerations
  6. 6. Test the upgrade in a non-production environment to verify compatibility with your configuration and backend services
  7. 7. Schedule maintenance window and deploy the upgrade following standard change management procedures
  8. 8. Verify the new version is running and test that JSON parsing functionality works correctly
Caveat Review HAProxy changelog for your version range for any configuration or behavior changes; test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aloha Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11230 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data