Hello, The libssh2 library appears to be relevant in the Git for Windows build. Git depends on libcurl, and libcurl in turn depends on libssh2. However, even in the latest build, the version still appears to be 1.11.1, which I understand may be affected by vulnerability CVE-2026-55200. Is that correct? If so, when can a patched build be expected?

Kind regards, Martin Berner

Hi Martin,

On Tue, 7 Jul 2026, Berner Martin wrote:

For some definition of "relevant" ;-)

In Git for Windows, `libssh2` is only used by `libcurl`, and the way Git uses `libcurl`, there is no code path to using libssh2 functionality.

Therefore, I do not consider this critical enough to rush out a new Git for Windows version with a fix.

Besides...

That language "when can a patched build be expected" can very, very easily be perceived as quite entitled, and hence have the exact opposite effect of what you intended. You might want to be more careful in the future when you plan on not even offering to help while demanding work to be done in an Open Source project.

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?

Ciao, Johannes

Hello Johannes,

Thank you for clarifying that the use of Git in any way cannot lead to the use of libssh2 and that, therefore, the situation is not as critical as it initially seemed to me.

I apologize for the wording that may have sounded demanding. That was not my intention and was partly due to the translator. My days as a software developer are quite a long time ago, and the languages in which Git is written were not among those I worked with. As a result, my ability to contribute directly to the open-source community is rather limited. However, my employer supports the open-source community in other ways, so we are certainly not just beneficiaries.

Thank you also for your explanations regarding MSYS2.

Kind regards, Martin

-----Ursprüngliche Nachricht-----
Von: Johannes Schindelin <Johannes.Schindelin@gmx.de> 
Gesendet: Dienstag, 7. Juli 2026 13:56
An: Berner Martin <martin.berner@qualitasag.ch>
Cc: 'git@vger.kernel.org' <git@vger.kernel.org>
Betreff: Re: CVE-2026-55200 libssh2

Hi Martin,

On Tue, 7 Jul 2026, Berner Martin wrote:

For some definition of "relevant" ;-)

In Git for Windows, `libssh2` is only used by `libcurl`, and the way Git uses `libcurl`, there is no code path to using libssh2 functionality.

Therefore, I do not consider this critical enough to rush out a new Git for Windows version with a fix.

Besides...

That language "when can a patched build be expected" can very, very easily be perceived as quite entitled, and hence have the exact opposite effect of what you intended. You might want to be more careful in the future when you plan on not even offering to help while demanding work to be done in an Open Source project.

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?

Ciao, Johannes

Hi,

Johannes Schindelin wrote:

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.