Integrity loss via unchecked pack and index checksums
Published Feb 9, 2026 · Updated Feb 9, 2026
Improper integrity validation in go-git before 5.16.5 allows remote attackers to make clients consume corrupted Git pack data. Pack scanning did not verify trailer checksums, index decoding did not verify index checksums, and filesystem storage did not ensure that an index referenced the target pack hash. A user or application must fetch and process attacker-altered data; the documented result is repository-integrity loss and errors such as missing objects, not code execution.
Summary
What happened
Improper integrity validation in go-git before 5.16.5 allows remote attackers to make clients consume corrupted Git pack data. Pack scanning did not verify trailer checksums, index decoding did not verify index checksums, and filesystem storage did not ensure that an index referenced the target pack hash. A user or application must fetch and process attacker-altered data; the documented result is repository-integrity loss and errors such as missing objects, not code execution.
The record
- CVE
- CVE-2026-25934
- Published
- Feb 9, 2026
- Updated
- Feb 9, 2026
- Vendor
- go-git
- Product
- go-git
- Classifications
- CWE-354
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2026CVE publishedPublication date reported by the CVE source.
- Feb 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.16.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo