From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org, git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git for Windows 2.56.0(4)
Date: Mon, 26 Oct 2026 08:26:53 +0100 (CET) [thread overview]
Message-ID: <1MulqN-1wTpXS3ljv-017idF@mail.gmx.net> (raw)
Dear Git users,
I hereby announce that Git for Windows 2.56.0(4) is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.56.0(3) (October 22nd 2026)
This is another urgent security bug fix release, addressing
CVE-2026-111497.
Bug Fixes
* The executables included in the 32-bit MinGit had corrupt
code-signatures, which has been fixed.
* Upgrades the included brotli component to v1.2.1 to address
CVE-2026-111497.
Git-2.56.0.4-64-bit.exe | 4961a4a8cc778d8b6e00a5819e5fe4d078b754555aff7aedc2d77a5d74c2de80
Git-2.56.0.4-arm64.exe | e7dcc4adbb0eb373064598cd18bc75e60128707d816ead51cd9bd98e356f0075
PortableGit-2.56.0.4-64-bit.7z.exe | b1f3e52216e2ed6882d1bebfd4d3fdf319bec40d2edbbf9fd26ec4fd3fce7ed1
PortableGit-2.56.0.4-arm64.7z.exe | 044110f9d951858452ddb5e4b5415ea0f2b5b2598e794d6fec77fe28b9aa8cc0
MinGit-2.56.0.4-64-bit.zip | e3bf78351fe777fba47ddee5950082f8a98bb0f02604fdc7ba3ee2cb68ffa877
MinGit-2.56.0.4-arm64.zip | 70f7649f78088c1db1d2f3571ca46a04d5bef06e4e9d56d8ed7f9829e8c6c4db
MinGit-2.56.0.4-32-bit.zip | 6b3d71c7536d3c85baebaeb26d461e74c755895ccc1f4c817d0e289470419ccc
MinGit-2.56.0.4-busybox-64-bit.zip | c4f27d9356ef471dd9fea1f89e5c176cfff7c85b29912a00f3cc7fb59197a39f
MinGit-2.56.0.4-busybox-arm64.zip | 90f882fd91398dc2bd00f91af32401425815dd2f049a95fee68c9e783c311c7a
MinGit-2.56.0.4-busybox-32-bit.zip | 62dc9ff7c421a0742fd6128d91e9ebb2ec035fa21db6a6a2de0f2a018ca7831b
Git-2.56.0.4-64-bit.tar.bz2 | 0dae059764ba7c447c9604eb6cb0f4afaf2d90b003ecf1c8cf2dbe5a13e4442c
Git-2.56.0.4-arm64.tar.bz2 | e3903db2fea42263b4df0d2f581ca8e07ec1c7c9f878156a8d01284f35011642
Ciao,
Johannes
reply other threads:[~2026-10-26 7:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1MulqN-1wTpXS3ljv-017idF@mail.gmx.net \
--to=johannes.schindelin@gmx.de \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
/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