From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libcurl: Version bump. 8.20.0 -> 8.21.0
Date: Fri, 10 Jul 2026 08:21:13 +0200 [thread overview]
Message-ID: <20260710062113.492905-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260630190658.3665025-1-christian.melki@t2data.com>
Thanks, applied as e50495808bd0c003a9bc0043e6c3b031023d1c98.
Michael
[sent from post-receive hook]
On Fri, 10 Jul 2026 08:21:13 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Security fix galore. And the slew of bugfixes.
> https://curl.se/ch/8.21.0.html
>
> Plugs CVEs:
> CVE-2026-12064: proto-default skips SSH verification
> CVE-2026-11856: cross-origin Digest auth state leak
> CVE-2026-11586: WS Auto-PONG memory exhaustion
> CVE-2026-11564: Native CA trust persist
> CVE-2026-11352: QUIC zero-length UDP datagrams busy-loop
> CVE-2026-10536: HTTP/2 stream-dependency tree UAF
> CVE-2026-9547: SSH improper host validation
> CVE-2026-9546: sending old referer
> CVE-2026-9545: exposing HTTP/3 early data
> CVE-2026-9080: UAF after pause in socket callback
> CVE-2026-9079: stale proxy password leak
> CVE-2026-8932: incomplete mTLS config matching in conn reuse
> CVE-2026-8927: env-set cross-proxy Digest auth state leak
> CVE-2026-8926: password leak with netrc and user in URL
> CVE-2026-8925: SASL double-free
> CVE-2026-8924: trailing dot domain super cookie
> CVE-2026-8458: wrong reuse for different services
> CVE-2026-8286: wrong STARTTLS connection reuse
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260630190658.3665025-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libcurl.make b/rules/libcurl.make
> index 918dc71b6057..3c5b00adb9cf 100644
> --- a/rules/libcurl.make
> +++ b/rules/libcurl.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBCURL) += libcurl
> #
> # Paths and names
> #
> -LIBCURL_VERSION := 8.20.0
> -LIBCURL_SHA256 := 63fe2dc148ba0ceae89922ef838f7e5c946272c2e78b7c59fab4b79d3ce2b896
> +LIBCURL_VERSION := 8.21.0
> +LIBCURL_SHA256 := aa1b66a70eace83dc624508745646c08ae561de512ab403adffb93ac87fc72e6
> LIBCURL := curl-$(LIBCURL_VERSION)
> LIBCURL_SUFFIX := tar.xz
> LIBCURL_URL := https://curl.se/download/$(LIBCURL).$(LIBCURL_SUFFIX)
prev parent reply other threads:[~2026-07-10 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 19:06 [ptxdist] [PATCH] " Christian Melki
2026-07-10 6:21 ` Michael Olbrich [this message]
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=20260710062113.492905-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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