CVE-2026-110354

validatedZero produced an exploit or a check.

GHSA-vqpp-w68q-p3f5 ↗EUVD-2026-108000 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
HAProxy >= 3.0.0, < 3.0.30; >= 3.2.0, < 3.2.26; >= 3.3.0, < 3.3.17; >= 3.4.0, < 3.4.6; >= 3.5-dev, < 3.5-dev9; >= 3.0r1, < 3.0r1-362.1441; >= 3.2r1, < 3.2r1-378.1259; >= 3.3r1, < 3.3r1-377.1005; >= 3.2.0, < 3.2.17; >= 3.2.0, < 3.2.17-ee1; >= 3.0, < 3.0.16-ee17; >= 1.11, < 1.11.14-ee11
fixed in 3.0.30, 3.2.26, 3.3.17, 3.4.6, 3.5-dev9, 3.0r1-362.1441, 3.2r1-378.1259, 3.3r1-377.1005, 3.2.17, 3.2.17-ee1, 3.0.16-ee17, 1.11.14-ee11
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
ETK-2026-2383Zero's internal tracking ID, independent of the CVE number., permanent identifier
+30mTTV
14mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+30magent stopped
0
+10min
+20min

description

Affected HAProxy releases can be driven into persistent worker-thread CPU exhaustion by remote, unauthenticated requests using HTTP/1.1 chunked transfer encoding. Repeated requests may occupy all worker threads and prevent normal service until the process is restarted.

mitigation

Upgrade HAProxy to 3.0.30, 3.2.26, 3.3.17, 3.4.6, or 3.5-dev9, as appropriate. Upgrade affected Enterprise and Kubernetes Ingress Controller editions to their listed fixed releases.

fixed in 3.0.30, 3.2.26, 3.3.17, 3.4.6, 3.5-dev9, 3.0r1-362.1441, 3.2r1-378.1259, 3.3r1-377.1005, 3.2.17, 3.2.17-ee1, 3.0.16-ee17, 1.11.14-ee11

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 02:46Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-22 02:46Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-110354

{
  "etk_id": "ETK-2026-2383",
  "cve_id": "CVE-2026-110354",
  "display_id": "CVE-2026-110354",
  "ghsa_id": "GHSA-vqpp-w68q-p3f5",
  "euvd_id": "EUVD-2026-108000",
  "status": "published",
  "anchor_state": "anchored",
  "title": "HTTP/1.1 request parsing denial of service in HAProxy",
  "summary": "Affected HAProxy releases can be driven into persistent worker-thread CPU exhaustion by remote, unauthenticated requests using HTTP/1.1 chunked transfer encoding. Repeated requests may occupy all worker threads and prevent normal service until the process is restarted.",
  "mitigation": "Upgrade HAProxy to 3.0.30, 3.2.26, 3.3.17, 3.4.6, or 3.5-dev9, as appropriate. Upgrade affected Enterprise and Kubernetes Ingress Controller editions to their listed fixed releases.",
  "vendor": "HAProxy",
  "product": "HAProxy",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0.0, < 3.0.30",
        ">= 3.2.0, < 3.2.26",
        ">= 3.3.0, < 3.3.17",
        ">= 3.4.0, < 3.4.6",
        ">= 3.5-dev, < 3.5-dev9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.0.30",
        "3.2.26",
        "3.3.17",
        "3.4.6",
        "3.5-dev9"
      ],
      "package_name": "HAProxy",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0r1, < 3.0r1-362.1441",
        ">= 3.2r1, < 3.2r1-378.1259",
        ">= 3.3r1, < 3.3r1-377.1005"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.0r1-362.1441",
        "3.2r1-378.1259",
        "3.3r1-377.1005"
      ],
      "package_name": "HAProxy Enterprise Edition",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.2.0, < 3.2.17"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.2.17"
      ],
      "package_name": "HAProxy Kubernetes Ingress Controller",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.2.0, < 3.2.17-ee1",
        ">= 3.0, < 3.0.16-ee17",
        ">= 1.11, < 1.11.14-ee11"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.2.17-ee1",
        "3.0.16-ee17",
        "1.11.14-ee11"
      ],
      "package_name": "Kubernetes Ingress Controller Enterprise",
      "purl": null
    }
  ],
  "cwes": [
    835
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 14.467926366666667,
  "t0_at": "2026-10-22T02:46:38.255000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-22T03:16:09.904973+00:00",
      "days": 0.020505208020833332,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T02:46:38.255000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-22T02:46:38.255000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T02:46:38.255000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110354"
    }
  }
}

published 2026-10-22 03:01Z
last change 2026-10-22 07:40Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.