From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libssh: security bump version to 0.12.1
Date: Tue, 21 Jul 2026 21:46:54 +0200 [thread overview]
Message-ID: <5f39afa856079fb0ad623a661f26685c@free.fr> (raw)
In-Reply-To: <20260721184316.3523325-1-bernd@kuhls.net>
On 21/07/2026 20:43, Bernd Kuhls wrote:
> https://gitlab.com/libssh/libssh-mirror/-/tags/libssh-0.12.1
> https://www.libssh.org/2026/07/21/libssh-0-12-1-and-0-11-5-security-releases/
>
> Fixes the following security problems:
>
> CVE-2026-15370: Stack buffer overflow in SFTP server longname
> construction
> CVE-2026-59842: Information disclosure via short GSSAPI Curve25519
> public key
> CVE-2026-59843: Denial of service via zero advertised channel packet
> size
> CVE-2026-59844: Denial of service via oversized SFTP read length
> CVE-2026-59845: Denial of service via unchecked ProxyCommand fork()
> failure
> CVE-2026-59846: Information disclosure via ProxyCommand %r username
> expansion
> CVE-2026-59847: Integrity downgrade via OpenSSL AES-GCM tag
> verification
> CVE-2026-59848: Denial of service via SFTP responses with unknown
> request IDs
> CVE-2026-59849: Denial of service via automatic certificate
> authentication loop
> CVE-2026-59850: Use-after-free via data callbacks on closed channels
> CVE-2026-59851: Authentication bypass via missing GSSAPI principal
> check
> Zero-initialize every ssh_string
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-21 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 18:43 [Buildroot] [PATCH 1/1] package/libssh: security bump version to 0.12.1 Bernd Kuhls
2026-07-21 19:46 ` Julien Olivain via buildroot [this message]
2026-07-31 12:05 ` Thomas Perale 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=5f39afa856079fb0ad623a661f26685c@free.fr \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=ju.o@free.fr \
/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