fix(deps): update module github.com/go-git/go-git/v5 to v5.17.1 [security]#218
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
fix(deps): update module github.com/go-git/go-git/v5 to v5.17.1 [security]#218renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
…rity] Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
5073999 to
ed7d5c7
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.14.0→v5.17.1GitHub Vulnerability Alerts
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.CVE-2026-33762
Impact
go-git’s index decoder for format version 4 fails to validate the path name prefix length before applying it to the previously decoded path name. A maliciously crafted index file can trigger an out-of-bounds slice operation, resulting in a runtime panic during normal index parsing.This issue only affects Git index format version 4. Earlier formats (
go-gitsupports onlyv2andv3) are not vulnerable to this issue.An attacker able to supply a crafted
.git/indexfile can cause applications using go-git to panic while reading the index. If the application does not recover from panics, this results in process termination, leading to a denial-of-service (DoS) condition.Exploitation requires the ability to modify or inject a Git index file within the local repository in disk. This typically implies write access to the
.gitdirectory.Patches
Users should upgrade to
v5.17.1, or the latestv6pseudo-version, in order to mitigate this vulnerability.Credit
go-git maintainers thank @kq5y for finding and reporting this issue privately to the
go-gitproject.CVE-2026-34165
Impact
A vulnerability has been identified in which a maliciously crafted
.idxfile can cause asymmetric memory consumption, potentially exhausting available memory and resulting in a Denial of Service (DoS) condition.Exploitation requires write access to the local repository's
.gitdirectory, it order to create or alter existing.idxfiles.Patches
Users should upgrade to
v5.17.1, or the latestv6pseudo-version, in order to mitigate this vulnerability.Credit
The go-git maintainers thank @kq5y 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.17.1Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.17.0...v5.17.1
v5.17.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.5...v5.17.0
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
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.