Skip to content

build: Update module github.com/go-git/go-git/v5 to v5.16.5 [SECURITY] (releases/v5.x)#1839

Merged
pjbgf merged 1 commit intoreleases/v5.xfrom
renovate/releases/v5.x-go-github.com-go-git-go-git-v5-vulnerability
Feb 10, 2026
Merged

build: Update module github.com/go-git/go-git/v5 to v5.16.5 [SECURITY] (releases/v5.x)#1839
pjbgf merged 1 commit intoreleases/v5.xfrom
renovate/releases/v5.x-go-github.com-go-git-go-git-v5-vulnerability

Conversation

@go-git-renovate
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/go-git/go-git/v5 v5.13.0v5.16.5 age confidence

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-git whereby data integrity values for .pack and .idx files were not properly verified. This resulted in go-git potentially consuming corrupted files, which would likely result in unexpected errors such as object not found.

For context, clients fetch packfiles from 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 by go-git, or the git cli, when new .pack files 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 for ssh://). 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 latest v6 pseudo-version, in order to mitigate this vulnerability.

Workarounds

In case updating to a fixed version of go-git is not possible, users can run git fsck from the git cli to check for data corruption on a given repository.

Credit

Thanks @​N0zoM1z0 for finding and reporting this issue privately to the go-git project.

Severity

  • CVSS Score: 4.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

References

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.5

Compare Source

What's Changed

Full Changelog: v5.16.4...v5.16.5

v5.16.4

Compare Source

What's Changed

Full Changelog: v5.16.3...v5.16.4

v5.16.3

Compare Source

What's Changed

  • internal: Expand regex to fix build [5.x] by @​baloo in #​1644
  • build: raise timeouts for windows CI tests and disable CIFuzz [5.x] by @​baloo in #​1646
  • plumbing: support commits extra headers, support jujutsu signed commit [5.x] by @​baloo in #​1633

Full Changelog: v5.16.2...v5.16.3

v5.16.2

Compare Source

What's Changed

  • utils: fix diff so subpaths work for sparse checkouts, fixes 1455 to releases/v5.x by @​kane8n in #​1567

Full Changelog: v5.16.1...v5.16.2

v5.16.1

Compare Source

What's Changed

New Contributors

Full Changelog: v5.16.0...v5.16.1

v5.16.0

Compare Source

What's Changed

Full Changelog: v5.15.0...v5.16.0

v5.15.0

Compare Source

What's Changed

Full Changelog: v5.14.0...v5.15.0

v5.14.0

Compare Source

What's Changed

⚠️ Note that this version requires Go 1.23, due to the bump to golang.org/x/[email protected] which 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: v5.13.2...v5.14.0

v5.13.2

Compare Source

What's Changed

Full Changelog: v5.13.1...v5.13.2

v5.13.1

Compare Source

What's Changed

Full Changelog: v5.13.0...v5.13.1


Configuration

📅 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 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@go-git-renovate go-git-renovate bot added the dependencies Pull requests that update a dependency file label Feb 10, 2026
@go-git-renovate
Copy link
Contributor Author

ℹ️ Artifact update notice

File name: cli/go-git/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 7 additional dependencies were updated

Details:

Package Change
github.com/Microsoft/go-winio v0.6.1 -> v0.6.2
github.com/ProtonMail/go-crypto v1.1.3 -> v1.1.6
github.com/cyphar/filepath-securejoin v0.2.5 -> v0.4.1
github.com/go-git/go-billy/v5 v5.6.0 -> v5.6.2
github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da -> v0.0.0-20241129210726-2c02b8208cf8
github.com/pjbgf/sha1cd v0.3.0 -> v0.3.2
github.com/skeema/knownhosts v1.3.0 -> v1.3.1

@pjbgf pjbgf merged commit 67c7006 into releases/v5.x Feb 10, 2026
30 of 32 checks passed
@pjbgf pjbgf deleted the renovate/releases/v5.x-go-github.com-go-git-go-git-v5-vulnerability branch February 10, 2026 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant