fix(deps): update module github.com/go-git/go-git/v5 to v5.16.5 [security]#549
Open
lunar-renovate wants to merge 1 commit intomasterfrom
Open
fix(deps): update module github.com/go-git/go-git/v5 to v5.16.5 [security]#549lunar-renovate wants to merge 1 commit intomasterfrom
lunar-renovate wants to merge 1 commit intomasterfrom
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
5b5e8dd to
90c7349
Compare
3f2bb6e to
258484d
Compare
258484d to
53f1186
Compare
e805e52 to
8e9e15a
Compare
dc83f4b to
9143d0a
Compare
9143d0a to
d49d632
Compare
d49d632 to
7e39a52
Compare
a7b40e5 to
c5ab85a
Compare
2474dfb to
a9b446d
Compare
a9b446d to
c67ab0c
Compare
c67ab0c to
4a4560d
Compare
4a4560d to
d7f0fc7
Compare
bfb789f to
75cce06
Compare
bcfccc7 to
ad13158
Compare
ad13158 to
54deed6
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
54deed6 to
c58c45a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.4.2→v5.16.5GitHub Vulnerability Alerts
CVE-2023-49569
Impact
A path traversal vulnerability was discovered in go-git versions prior to
v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved.Applications are only affected if they are using the ChrootOS, which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS or in-memory filesystems are not affected by this issue.
This is a
go-gitimplementation issue and does not affect the upstreamgitcli.Patches
Users running versions of
go-gitfromv4and above are recommended to upgrade tov5.11in order to mitigate this vulnerability.Workarounds
In cases where a bump to the latest version of
go-gitis not possible in a timely manner, we recommend limiting its use to only trust-worthy Git servers.Credit
Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.
CVE-2023-49568
Impact
A denial of service (DoS) vulnerability was discovered in go-git versions prior to
v5.11. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion ingo-gitclients.Applications using only the in-memory filesystem supported by
go-gitare not affected by this vulnerability.This is a
go-gitimplementation issue and does not affect the upstreamgitcli.Patches
Users running versions of
go-gitfromv4and above are recommended to upgrade tov5.11in order to mitigate this vulnerability.Workarounds
In cases where a bump to the latest version of
go-gitis not possible, we recommend limiting its use to only trust-worthy Git servers.Credit
Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.
References
CVE-2025-21613
Impact
An argument injection vulnerability was discovered in
go-gitversions prior tov5.13.Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the
filetransport protocol is being used, as that is the only protocol that shells out togitbinaries.Affected versions
Users running versions of
go-gitfromv4and above are recommended to upgrade tov5.13in order to mitigate this vulnerability.Workarounds
In cases where a bump to the latest version of
go-gitis not possible, we recommend users to enforce restrict validation rules for values passed in the URL field.Credit
Thanks to @vin01 for responsibly disclosing this vulnerability to us.
CVE-2025-21614
Impact
A denial of service (DoS) vulnerability was discovered in go-git versions prior to
v5.13. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion ingo-gitclients.This is a
go-gitimplementation issue and does not affect the upstreamgitcli.Patches
Users running versions of
go-gitfromv4and above are recommended to upgrade tov5.13in order to mitigate this vulnerability.Workarounds
In cases where a bump to the latest version of
go-gitis not possible, we recommend limiting its use to only trust-worthy Git servers.Credit
Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.
CVE-2026-25934
Impact
A vulnerability was discovered in
go-gitwhereby data integrity values for.packand.idxfiles were not properly verified. This resulted ingo-gitpotentially consuming corrupted files, which would likely result in unexpected errors such asobject not found.For context, clients fetch
packfilesfrom upstream Git servers. Those files contain a checksum of their contents, so that clients can perform integrity checks before consuming it. The pack indexes (.idx) are generated locally bygo-git, or thegitcli, when new.packfiles are received and processed. The integrity checks for both files were not being verified correctly.Note that the lack of verification of the packfile checksum has no impact on the trust relationship between the client and server, which is enforced based on the protocol being used (e.g. TLS in the case of
https://or known hosts forssh://). In other words, the packfile checksum verification does not provide any security benefits when connecting to a malicious or compromised Git server.Patches
Users should upgrade to
v5.16.5, or the latestv6pseudo-version, in order to mitigate this vulnerability.Workarounds
In case updating to a fixed version of
go-gitis not possible, users can run git fsck from thegitcli to check for data corruption on a given repository.Credit
Thanks @N0zoM1z0 for finding and reporting this issue privately to the
go-gitproject.Release Notes
go-git/go-git (github.com/go-git/go-git/v5)
v5.16.5Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.4...v5.16.5
v5.16.4Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.3...v5.16.4
v5.16.3Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.2...v5.16.3
v5.16.2Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.1...v5.16.2
v5.16.1Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.16.0...v5.16.1
v5.16.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.15.0...v5.16.0
v5.15.0Compare Source
What's Changed
releases/v5.xby @Javier-varez in #1482Full Changelog: go-git/go-git@v5.14.0...v5.15.0
v5.14.0Compare Source
What's Changed
golang.org/x/crypto@v0.35.0which mitigates the CVE above. User's that can't bump to Go 1.23 will need to remain on the previous v5.13.x release.Full Changelog: go-git/go-git@v5.13.2...v5.14.0
v5.13.2Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.13.1...v5.13.2
v5.13.1Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.13.0...v5.13.1
v5.13.0Compare Source
What's Changed
git clean -xflag. by @msuozzo in #995git clean -xflag." by @pjbgf in #1129Untrackedwhile it is committed by @rodrigocam in #1023New Contributors
Full Changelog: go-git/go-git@v5.12.0...v5.13.0
v5.12.0Compare Source
What's Changed
FastForwardMergesupport by @pjbgf in #1044New Contributors
Full Changelog: go-git/go-git@v5.11.0...v5.12.0
v5.11.0Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.10.1...v5.11.0
v5.10.1Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.10.0...v5.10.1
v5.10.0Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.9.0...v5.10.0
v5.9.0Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.8.1...v5.9.0
v5.8.1Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.8.0...v5.8.1
v5.8.0Compare Source
What's Changed
doAddDirectoryby @ThinkChaos in #702Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Run
lunarctl renovate refresh -r lunarway/release-managerto trigger refresh immediately. Check renovate-refresh-cli for more details.This PR has been generated by Renovate Bot.