From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Todd Zullinger <tmz@pobox.com>, Junio C Hamano <gitster@pobox.com>
Cc: Patrick Steinhardt <ps@pks.im>,
git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git 2.56.1 and friends
Date: Wed, 11 Nov 2026 11:54:18 +0530 [thread overview]
Message-ID: <e12a9cd6-d61a-4e80-a459-954c4b26724f@gmail.com> (raw)
In-Reply-To: <20261110221253.DBFncUIG@teonanacatl.net>
Hi Todd,
On 11/11/26 03:42, Todd Zullinger wrote:
> Junio C Hamano wrote:
>> Credit for organizing the set of these releases goes to Johannes
>> Schindelin. Credit for finding the vulnerabilities goes to Luke
>> Martin and pwn2addr. Credit for fixing them goes to Toon Claes,
>> Karthik Nayak, and Kaartic Sivaraam. The xdiff hardening is based
>> on a patch by Jeff King, with help from Toon Claes and Christian
>> Couder.
>
> Many thanks to all for the effort, including Junio.
>
Indeed. Thank you all for the efforts!
>> This addresses the security issues CVE-2026-111760, CVE-2026-113408,
>> CVE-2026-114466, CVE-2026-114467, CVE-2026-114469 and CVE-2026-105437.
>>
>> * CVE-2026-113408:
>>
>> It is possible for a server to advertise an unborn HEAD that contains
>> path-traversal characters (e.g., `refs/heads/../../../TARGET`). With
>> the files ref backend that can lead to ref-updating actions to write
>> to unwanted files.
>>
>> See <https://gitlab.com/gitlab-org/git/-/work_items/809> for details.
>
> FWIW, this and the other GitLab work item links appear to be
> inaccessible to normal users. I'm guessing that's not the
> intent.
>
> I added Patrick to the Cc as one of the folks who may be
> able to poke the right folks at GitLab to open them up?
>
Thank you for pointing it out. It was indeed not the intention. Those
work items are accessible now.
--
Sivaraam
next prev parent reply other threads:[~2026-11-11 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 18:03 [ANNOUNCE] Git 2.56.1 and friends Junio C Hamano
2026-11-10 22:12 ` Todd Zullinger
2026-11-11 6:24 ` Kaartic Sivaraam [this message]
2026-11-11 14:02 ` Toon Claes
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=e12a9cd6-d61a-4e80-a459-954c4b26724f@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ps@pks.im \
--cc=tmz@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.