Git development
 help / color / mirror / Atom feed
From: Todd Zullinger <tmz@pobox.com>
To: "Person, Tim" <Tim.Person@personent.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Security Vulnerability in Git 2.54.0/OpenSSL 3.5.6 Status
Date: Sat, 27 Jun 2026 17:07:18 -0400	[thread overview]
Message-ID: <20260627210718.zl0eH_Sc@teonanacatl.net> (raw)
In-Reply-To: <SN4P221MB0713994458A94BFCB51F7AC494EA2@SN4P221MB0713.NAMP221.PROD.OUTLOOK.COM>

Hi,

Person, Tim wrote:
> I am writing to determine when Git plans to release an
> update installer to patch the security vulnerability in
> Git 2.54.0 because of the included OpenSSL executable.
> This vulnerability is rated "Critical" in the CVE
> (https://www.cve.org/CVERecord?id=CVE-2026-34182). An
> updated version of the OpenSSL.exe fixing this problem has
> been available since 06/12/2026. I am just wondering
> if/when you plan to address this major security issue.

The Git project does not distribute any binaries.  You
likely want to direct this to the Git for Windows project¹.

That said, it's not even clear to me that the CVE you
reference affects git's usage of OpenSSL.

From a little skimming, the issue affects use of CMS (which
is something like the successor to S/MIME, as far as I can
tell).

The only place where git gets close to that area is if you
configure it to use x509 as gpg.program.  And then git uses
gpgsm, which is not affected by the CVE in OpenSSL.

¹ https://gitforwindows.org/

-- 
Todd

  reply	other threads:[~2026-06-27 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 19:18 Security Vulnerability in Git 2.54.0/OpenSSL 3.5.6 Status Person, Tim
2026-06-27 21:07 ` Todd Zullinger [this message]
2026-06-27 21:17   ` Person, Tim

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=20260627210718.zl0eH_Sc@teonanacatl.net \
    --to=tmz@pobox.com \
    --cc=Tim.Person@personent.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