From: Todd Zullinger <tmz@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Berner Martin <martin.berner@qualitasag.ch>, git@vger.kernel.org
Subject: Re: CVE-2026-55200 libssh2
Date: Tue, 7 Jul 2026 12:24:52 -0400 [thread overview]
Message-ID: <20260707162452._tjDEpzZ@teonanacatl.net> (raw)
In-Reply-To: <26531fd0-4a21-c8ef-84a9-25c871cde303@gmx.de>
Hi,
Johannes Schindelin wrote:
> Back to your question why Git for Windows still only includes v1.11.1 of
> libssh2. The answer is rather trivial: MSYS2 (on which Git for Windows is
> based through a healthy collaboration) includes only that version:
>
> https://packages.msys2.org/base/mingw-w64-libssh2
>
> And the reason for _that_ might be rooted in the fact that both the
> repository as well as the website of libssh2 list that as the very latest
> available version:
>
> - https://github.com/libssh2/libssh2/releases/latest currently redirects
> to https://github.com/libssh2/libssh2/releases/tag/libssh2-1.11.1
>
> - https://libssh2.org/ says:
>
> Download
> libssh2 1.11.1, released on 2024-10-16. *link to Changelog*
>
> Easy explanation, right?
Indeed. :)
An upstream issue requesting a release to aid in the
distribution of these fixes was filed about 2 months ago
(after CVE-2026-7598, before CVE-2026-55200 and some
others):
https://github.com/libssh2/libssh2/issues/1925
That may be worth tracking for anyone curious.
--
Todd
prev parent reply other threads:[~2026-07-07 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 8:38 CVE-2026-55200 libssh2 Berner Martin
2026-07-07 11:55 ` Johannes Schindelin
2026-07-07 13:25 ` AW: " Berner Martin
2026-07-07 16:24 ` Todd Zullinger [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=20260707162452._tjDEpzZ@teonanacatl.net \
--to=tmz@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=martin.berner@qualitasag.ch \
/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