CVE-2026-25934
ADVISORY - githubSummary
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.
Common Weakness Enumeration (CWE)
Improper Validation of Integrity Check Value
Improper Validation of Integrity Check Value
GitHub
2.8
CVSS SCORE
4.3medium| Package | Type | OS Name | OS Version | Affected Ranges | Fix Versions |
|---|---|---|---|---|---|
| github.com/go-git/go-git/v5 | golang | - | - | <=5.16.4 | 5.16.5 |
| github.com/go-git/go-git/v5 | golang | - | - | <0.0.0-20260209124510-48a1ae05eec4 | 0.0.0-20260209124510-48a1ae05eec4 |
CVSS:3 Severity and metrics
The CVSS metrics represent different qualitative aspects of a vulnerability that impact the overall score, as defined by the CVSS Specification.
The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone). One example of an Adjacent attack would be an ARP (IPv4) or neighbor discovery (IPv6) flood leading to a denial of service on the local LAN segment (e.g., CVE-2013-6014).
Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.
The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.
An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
There is no loss of confidentiality.
Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
There is no impact to availability within the impacted component.
NIST
2.8
CVSS SCORE
4.3mediumDebian
-
Ubuntu
2.8
CVSS SCORE
4.3mediumGoLang
-
Chainguard
CGA-v36v-c63w-r62j
-
minimos
MINI-22pg-qg98-fhc2
-
minimos
MINI-26rf-c957-jwq7
-
minimos
MINI-2mgf-5gxq-8qh6
-
minimos
MINI-2v3h-hfqq-74w6
-
minimos
MINI-3rgq-rwq9-p89c
-
minimos
MINI-49rx-crg6-23p3
-
minimos
MINI-52qg-vxr3-844j
-
minimos
MINI-5599-f585-gqqv
-
minimos
MINI-587f-h53p-pv58
-
minimos
MINI-5g3q-89m7-vhw3
-
minimos
MINI-5g5x-243c-7x7x
-
minimos
MINI-5hj8-2j6x-2rxm
-
minimos
MINI-5j4m-9mv2-hccx
-
minimos
MINI-6892-3h87-46m2
-
minimos
MINI-697h-p9cj-pmc6
-
minimos
MINI-6c9v-pv6g-r2cw
-
minimos
MINI-6cjp-j2hw-xhjh
-
minimos
MINI-6j8q-5qfx-w98r
-
minimos
MINI-6rxx-2862-f586
-
minimos
MINI-6xgf-mqj2-q9w6
-
minimos
MINI-87v7-cjr3-h2r9
-
minimos
MINI-8fc5-36ww-x6wh
-
minimos
MINI-8r3v-868g-hg85
-
minimos
MINI-936f-gx74-7j38
-
minimos
MINI-9584-94x7-7w46
-
minimos
MINI-c4h7-hx3m-r3mj
-
minimos
MINI-cf6x-jx4g-3qhc
-
minimos
MINI-f74r-26f8-mqph
-
minimos
MINI-fgfh-9v8v-qmv6
-
minimos
MINI-fxxv-37mv-hfhc
-
minimos
MINI-gj88-m48r-gxq2
-
minimos
MINI-gv87-xgh8-5q62
-
minimos
MINI-jcm4-4rq9-ffjx
-
minimos
MINI-jx36-hcxf-xqcm
-
minimos
MINI-m5x4-3w8p-2hc6
-
minimos
MINI-mp7j-982w-27w9
-
minimos
MINI-mqxq-v959-jhw5
-
minimos
MINI-mw9r-mv5h-ffcq
-
minimos
MINI-p4fv-v929-q6pv
-
minimos
MINI-p6mp-f63x-3mr9
-
minimos
MINI-pmrx-rwq6-c7j5
-
minimos
MINI-pqx6-x442-75pf
-
minimos
MINI-pvjp-4gwx-cg9m
-
minimos
MINI-q5wh-fhpf-7f8c
-
minimos
MINI-qmgm-jmf9-q82v
-
minimos
MINI-qmvf-9fh4-hq54
-
minimos
MINI-rhg2-6rm3-rvc9
-
minimos
MINI-rqjv-7887-vcqj
-
minimos
MINI-rw6x-hq56-cf94
-
minimos
MINI-v52x-xwv9-9jq2
-
minimos
MINI-vr2x-vpr6-4v7q
-
minimos
MINI-w3pg-mpcv-54vg
-
minimos
MINI-w6p4-wxvj-67fm
-
minimos
MINI-wm23-7vgx-x965
-
minimos
MINI-ww5h-2cqf-j9x4
-
minimos
MINI-x6jq-jj87-4hr5
-
minimos
MINI-x75c-6xm4-pvcq
-
minimos
MINI-xfxw-3c37-4f5h
-
minimos
MINI-xgj4-f298-7gr2
-
minimos
MINI-xhv8-967g-jrw8
-
minimos
MINI-xp3q-69ff-6233
-
minimos
MINI-xvph-hc82-gvq7
-