CVE-2026-25934: go-git improperly verifies data integrity values for .idx and .pack files
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.
Published Feb 10, 2026
Affected packages
github.com/go-git/go-git/v5
- Ecosystem
- Go
- Affected
- <= 5.16.4
- Fixed in
- 5.16.5
- Check
go list -m github.com/go-git/go-git/v5
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to N0zoM1z0.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-71556
go-git: Worktree operations may follow symlinks
high7.1Aug 7, 2026CVE-2026-71557
go-git: Malicious reference names may modify files outside the reference storage
medium6.3Aug 7, 2026GHSA-w5pp-99ch-qj29
go-git: Malformed Git object data may cause panics or resource exhaustion
medium6.5May 29, 2026CVE-2026-45570
go-git: Improper single-quote escaping in go-git SSH transport
low2.3No fixMay 19, 2026CVE-2026-45571
go-git: Crafted repositories may modify main and submodule .git directories
medium5.4No fixMay 19, 2026CVE-2026-45022
go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
high7.0May 11, 2026
