p PatchFirst

PatchFirst · Свежие уязвимости

haproxy 3.4.0: известные уязвимости

Известных уязвимостей, затрагивающих haproxy 3.4.0: 5. Сравните исправленные версии ниже с установленной у вас.

RSS ↗
Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 5

  1. CVE-2026-110353

    Высокий · CVSS 7.5EPSS 0,68%Есть исправление

    CVE-2026-110353

    HAProxy 3.2 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (worker-thread CPU exhaustion) via a truncated HTTP/2 PING frame. h2c_handle_ping in src/mux_h2.c does not check for a short read, unlike the other H2 frame handlers. Because the incomplete frame cannot be processed, its data is never consumed, and the H2 multiplexer tasklet is repeatedly woken by that pending data without making progress. The CPU spins until timeout http-request closes the connection, and an attacker opening many such connections can sustain high CPU usage.

    • Обновитесь до 3.4.6
    Опубликовано Обновлено
  2. CVE-2026-110354

    Высокий · CVSS 7.5EPSS 0,76%Есть исправление

    CVE-2026-110354

    HAProxy 3 before 3.4.6 allows a remote unauthenticated attacker to cause a denial of service (persistent worker-thread CPU exhaustion) via an HTTP/1.1 chunked request. Although the H1 multiplexer drains the request before closing the stream, the parser repeatedly re-processes the same bytes without making progress. The affected thread stays busy at 100% CPU after timeouts expire and after the client disconnects, and repeated requests can consume all worker threads until the process is restarted.

    • Обновитесь до 3.4.6
    Опубликовано Обновлено
  3. CVE-2026-90678

    Высокий · CVSS 7.5EPSS 0,77%Нет опубликованного исправления

    CVE-2026-90678

    An issue was discovered in HAProxy 3.3.0 through 3.4.4 and in 3.5-dev1 through 3.5-dev5. Exploitation requires an HTTP/3 frontend: HAProxy must be built with QUIC support and configured with a QUIC bind listener, and the affected traffic must reach a backend over HTTP/1.1 using chunked transfer coding on a reused connection. Under those conditions, when an HTTP/3 request carries no Content-Length header, the HTTP/3 multiplexer credits the length declared in a DATA frame header to the stream endpoint's known-input-payload estimate at the moment the frame header is decoded, before the payload has been received, and that declared length is emitt

    Опубликовано Обновлено
  4. CVE-2026-55204

    Высокий · CVSS 8.7EPSS 0,48%Нет опубликованного исправления

    HAProxy - NULL Pointer Dereference in hpack_dht_insert Function

    HAProxy through 3.4.0, fixed in commit 9a6d1fe, contains a null pointer dereference vulnerability in hpack_dht_insert() within src/hpack-tbl.c that fails to validate the return value of hpack_dht_defrag() when the memory pool is exhausted. An attacker can trigger HPACK dynamic table insertions under memory pressure to dereference a NULL pointer and crash HAProxy worker processes, causing denial of service.

  5. CVE-2026-55203

    Критический · CVSS 9.0EPSS 0,33%Нет опубликованного исправления

    HAProxy - Integer Overflow in FCGI Demux Record Length Field

    HAProxy through 3.4.0, fixed in commit 5985276, contains an integer overflow vulnerability in the fcgi_conn structure's drl field that allows buffer misparse as new FCGI record headers. When contentLength is 65535 and paddingLength is 1 or more, the drl field wraps to 0, causing incorrect record consumption and allowing malicious FastCGI backends to desynchronize the FCGI framing parser, potentially causing request routing errors, response smuggling, or memory safety issues.

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →