FKIE_CVE-2026-109575

Vulnerability from fkie_nvd - Published: 2026-10-12 20:17 - Updated: 2026-10-13 17:17
Severity
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
In HAProxy Data Plane API 2.2.0 through 3.4.3 (and corresponding Enterprise Edition releases), Server.ConfigureAPI() has process-global authentication logic that improperly drops security controls across multiple transport types. When a TLS Certificate Authority (tls_ca) is configured and a numeric TLS port (tls_port) is specified, the application globally disables Basic authentication on its shared internal request handler. Because this handler is shared concurrently among HTTP, HTTPS, and UNIX domain socket listeners, and mutual TLS (mTLS) client certificate verification (tls.RequireAndVerifyClientCert) is enforced exclusively on the HTTPS server path, all other simultaneously active non-mTLS listeners fail open. Consequently, an unauthenticated attacker capable of reaching an affected HTTP or UNIX management endpoint can completely bypass credentials to gain full API administrative access. This allows unauthorized remote or local actors to read sensitive, cleartext HAProxy configuration data or replace the managed configuration entirely via the raw configuration endpoint. This has been fixed in versions 3.4.4, 3.3.9, 3.2.17, 3.0.25, 2.9.29, and their respective EE backports by migrating to a per-request TLS connection-state validation model.
References
cve@mitre.orghttps://github.com/haproxytech/dataplaneapi/commit/c3ae4e3ccff5490d44650565e445c4b15e8aff8c
cve@mitre.orghttps://github.com/haproxytech/dataplaneapi/releases/tag/v3.4.4
cve@mitre.orghttps://www.haproxy.com/documentation/haproxy-data-plane-api/
cve@mitre.orghttps://www.haproxy.com/documentation/haproxy-data-plane-api/community/changelog/#version-3.4
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "packageName": "dataplaneapi",
          "product": "Data Plane API EE",
          "vendor": "HAProxy",
          "versions": [
            {
              "changes": [
                {
                  "at": "2.9.29-ee1",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "2.9.28-ee1",
              "status": "affected",
              "version": "2.2.0-ee1",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.0.25-ee1",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.0.24-ee1",
              "status": "affected",
              "version": "3.0-ee",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.2.17-ee1",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.2.16-ee1",
              "status": "affected",
              "version": "3.1-ee",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.3.9-ee1",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.3.8-ee1",
              "status": "affected",
              "version": "3.3-ee",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.4.4-ee1",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.4.3-ee2",
              "status": "affected",
              "version": "3.4-ee",
              "versionType": "custom"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageName": "dataplaneapi-ee",
          "product": "Data Plane API CE",
          "repo": "https://github.com/haproxytech/dataplaneapi",
          "vendor": "HAProxy",
          "versions": [
            {
              "changes": [
                {
                  "at": "2.9.29",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "2.9.28",
              "status": "affected",
              "version": "2.2.0",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.0.25",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.0.24",
              "status": "affected",
              "version": "3.0.0",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.2.17",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.2.16",
              "status": "affected",
              "version": "3.1.0",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.3.9",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.3.8",
              "status": "affected",
              "version": "3.3.0",
              "versionType": "custom"
            },
            {
              "changes": [
                {
                  "at": "3.4.4",
                  "status": "unaffected"
                }
              ],
              "lessThanOrEqual": "3.4.3",
              "status": "affected",
              "version": "3.4.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "cve@mitre.org"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In HAProxy Data Plane API 2.2.0 through 3.4.3 (and corresponding Enterprise Edition releases), Server.ConfigureAPI() has process-global authentication logic that improperly drops security controls across multiple transport types. When a TLS Certificate Authority (tls_ca) is configured and a numeric TLS port (tls_port) is specified, the application globally disables Basic authentication on its shared internal request handler. Because this handler is shared concurrently among HTTP, HTTPS, and UNIX domain socket listeners, and mutual TLS (mTLS) client certificate verification (tls.RequireAndVerifyClientCert) is enforced exclusively on the HTTPS server path, all other simultaneously active non-mTLS listeners fail open. Consequently, an unauthenticated attacker capable of reaching an affected HTTP or UNIX management endpoint can completely bypass credentials to gain full API administrative access. This allows unauthorized remote or local actors to read sensitive, cleartext HAProxy configuration data or replace the managed configuration entirely via the raw configuration endpoint. This has been fixed in versions 3.4.4, 3.3.9, 3.2.17, 3.0.25, 2.9.29, and their respective EE backports by migrating to a per-request TLS connection-state validation model."
    }
  ],
  "id": "CVE-2026-109575",
  "lastModified": "2026-10-13T17:17:29.160",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 9.8,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.9,
        "source": "cve@mitre.org",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-109575",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-10-13T15:59:06.374302Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-10-12T20:17:09.443",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/haproxytech/dataplaneapi/commit/c3ae4e3ccff5490d44650565e445c4b15e8aff8c"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/haproxytech/dataplaneapi/releases/tag/v3.4.4"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://www.haproxy.com/documentation/haproxy-data-plane-api/"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://www.haproxy.com/documentation/haproxy-data-plane-api/community/changelog/#version-3.4"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Received",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-306"
        }
      ],
      "source": "cve@mitre.org",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.