Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Thomas Perale <thomas.perale@mind.be>
Subject: [Buildroot] [PATCH] package/haproxy: security bump to version 3.4.8
Date: Thu, 19 Nov 2026 09:33:29 +0100	[thread overview]
Message-ID: <20261119083331.195248-1-peter@korsgaard.com> (raw)

Fixes the following vulnerabilities:

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

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.

In addition to a number of bugfixes. Release notes:

3.4.5: https://www.mail-archive.com/haproxy@formilux.org/msg47506.html
3.4.6: https://www.mail-archive.com/haproxy@formilux.org/msg47531.html
3.4.7: https://www.mail-archive.com/haproxy@formilux.org/msg47598.html
3.4.8: https://www.mail-archive.com/haproxy@formilux.org/msg47800.html

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 package/haproxy/haproxy.hash | 4 ++--
 package/haproxy/haproxy.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/package/haproxy/haproxy.hash b/package/haproxy/haproxy.hash
index 9f3a08c500..fd0c4ce4d3 100644
--- a/package/haproxy/haproxy.hash
+++ b/package/haproxy/haproxy.hash
@@ -1,5 +1,5 @@
-# From: http://www.haproxy.org/download/3.4/src/haproxy-3.4.4.tar.gz.sha256
-sha256  b0c5053c4d46840ecdee3925736fe9a3de6472559b43c69183d70e593d9133df  haproxy-3.4.4.tar.gz
+# From: http://www.haproxy.org/download/3.4/src/haproxy-3.4.8.tar.gz.sha256
+sha256  024bd521a6cbbe32b426853147e6bbd6a89b107c5a34144846193fee5b7c6ed1  haproxy-3.4.8.tar.gz
 # Locally computed:
 sha256  0717ca51fceaa25ac9e5ccc62e0c727dcf27796057201fb5fded56a25ff6ca28  LICENSE
 sha256  5df07007198989c622f5d41de8d703e7bef3d0e79d62e24332ee739a452af62a  doc/lgpl.txt
diff --git a/package/haproxy/haproxy.mk b/package/haproxy/haproxy.mk
index de2df549b1..fa24515740 100644
--- a/package/haproxy/haproxy.mk
+++ b/package/haproxy/haproxy.mk
@@ -5,7 +5,7 @@
 ################################################################################
 
 HAPROXY_VERSION_MAJOR = 3.4
-HAPROXY_VERSION = $(HAPROXY_VERSION_MAJOR).4
+HAPROXY_VERSION = $(HAPROXY_VERSION_MAJOR).8
 HAPROXY_SITE = http://www.haproxy.org/download/$(HAPROXY_VERSION_MAJOR)/src
 HAPROXY_LICENSE = GPL-2.0+ and LGPL-2.1+ with exceptions
 HAPROXY_LICENSE_FILES = LICENSE doc/lgpl.txt doc/gpl.txt
-- 
2.47.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-11-19  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  8:33 Peter Korsgaard [this message]
2026-11-19 13:05 ` [Buildroot] [PATCH] package/haproxy: security bump to version 3.4.8 Marcus Hoffmann via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261119083331.195248-1-peter@korsgaard.com \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.perale@mind.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox