From: Toon Claes <toon@iotcl.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
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 15:02:14 +0100 [thread overview]
Message-ID: <874idn5uvt.fsf@dev.null.iotcl.com.invalid> (raw)
In-Reply-To: <e12a9cd6-d61a-4e80-a459-954c4b26724f@gmail.com>
>>> * 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.
Yeah, I was planning to open them up ASAP, but I wasn't around my
computer around the time this release came out. I did open them around
midnight CET. Thanks for pointing that out.
--
Laters,
Toon
prev parent reply other threads:[~2026-11-11 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 18:03 Junio C Hamano
2026-11-10 22:12 ` Todd Zullinger
2026-11-11 6:24 ` Kaartic Sivaraam
2026-11-11 14:02 ` Toon Claes [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=874idn5uvt.fsf@dev.null.iotcl.com.invalid \
--to=toon@iotcl.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®