fix(deps): Update module github.com/go-git/go-git/v5 to v5.16.5 [SECURITY]#5485
Merged
renovate-sh-app[bot] merged 1 commit intomainfrom Feb 10, 2026
Conversation
…RITY] | datasource | package | from | to | | ---------- | --------------------------- | ------- | ------- | | go | github.com/go-git/go-git/v5 | v5.16.2 | v5.16.5 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
Contributor
🔍 Dependency Reviewgithub.com/go-git/go-git/v5 v5.16.2 → v5.16.5 — ✅ Safe
Evidence (release notes):
Required code changes:
Suggested validation:
Notes
|
blewis12
approved these changes
Feb 10, 2026
Draft
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.16.2→v5.16.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub 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.go-git improperly verifies data integrity values for .idx and .pack files
CVE-2026-25934 / GHSA-37cx-329c-33x3
More information
Details
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.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
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
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 these updates again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.