MediumGHSA-37cx-329c-33x3CVE-2026-25934GO-2026-4473

go-git improperly verifies data integrity values for .idx and .pack files

Published 10 Feb 2026 · Updated 10 Sept 2026

Is your project on an affected github.com/go-git/go-git/v5?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<5.16.5
Fixed in
5.16.5
Update to the fixed version for your release line, for example:go get github.com/go-git/go-git/v5@v5.16.5

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.

Is GHSA-37cx-329c-33x3 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/go-git/go-git/v5, and gives you the command that fixes it.

More advisories for github.com/go-git/go-git/v5

  • LowCVE-2026-71556Worktree operations may follow symlinks in github.com/go-git/go-git · 18 Aug 2026
  • LowCVE-2026-71557Path traversal via crafted reference names in github.com/go-git/go-git · 18 Aug 2026
  • MediumCVE-2026-71557go-git: Malicious reference names may modify files outside the reference storage · 7 Aug 2026
  • HighCVE-2026-71556go-git: Worktree operations may follow symlinks · 7 Aug 2026
  • LowCVE-2026-45022Go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation in github.com/go-git/go-git · 24 Jul 2026
  • LowCVE-2026-41506Go-git: Credential leak via cross-host redirect in smart HTTP transport in github.com/go-git/go-git · 24 Jul 2026
All 27 advisories for github.com/go-git/go-git/v5

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.