public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Luis Alvarado <luis.alvarado.torres@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: CVE-2025-66476
Date: Thu, 22 Jan 2026 10:09:29 -0800	[thread overview]
Message-ID: <xmqqikcto6xy.fsf@gitster.g> (raw)
In-Reply-To: <CALFwtBbK6sNo0swy5k_+jgcKQmOpw3b=o8_UKhvLhtYYLqoUow@mail.gmail.com> (Luis Alvarado's message of "Thu, 22 Jan 2026 11:40:30 -0500")

Luis Alvarado <luis.alvarado.torres@gmail.com> writes:

> I need some help or guidance on how to remediate this vulnerability.
> We have a customer with Git, which includes VIM and is vulnerable to
> CVE-2025-66476. However, the GIT version for Windows was last updated
> in November 2025. How can I remediate this issue, is there a way to
> update VIM without updating git? if so , how.

The Git project does not ship any binary, not even Git binary, let
alone Vim binary.  We work on and ship only the source code of Git.

If you are getting your vim as part of the windows port of Git,
please redirect your inquiry to the Git for Windows project; you can
probably reach out to them at their issue tracker at

    https://github.com/git-for-windows/git/issues.

Please be sure to search first before asking, since the maintainer
of the project is busy.

Thanks.

      reply	other threads:[~2026-01-22 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 16:40 CVE-2025-66476 Luis Alvarado
2026-01-22 18:09 ` Junio C Hamano [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=xmqqikcto6xy.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=luis.alvarado.torres@gmail.com \
    /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