CVE-2026-25934
Go-Git Project Go-Git ≤ 5.16.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2026-25934 is a medium-severity Improper Validation of Integrity Check Value (CWE-354) vulnerability in Go-Git Project Go-Git. Its CVSS base score is 4.3 (Medium).
Operationally, ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-7 (Software, Firmware, and Information Integrity) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6247
Vulnerability Data
go-git is a highly extensible git implementation library written in pure Go. Prior to 5.16.5, 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…
more
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. This vulnerability is fixed in 5.16.5.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Insufficient information to map techniques.CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
- 10 hardening rules · 4 OS baselines
V10.4.12
Mitigating Controls (NIST 800-53 r5) AI
Directly requires verification of information integrity (including checksums on received pack/idx files) before use, preventing consumption of corrupted objects.
Requires validation of input data; integrity-check failures for fetched packfiles are a specific case of missing input validation.
Requires integrity protection for transmitted data, which includes verifying the checksums supplied with packfiles from upstream Git servers.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data at rest.
Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data in transit.
Mandates pre-acquisition integrity assessment, addressing only the initial portion of the weakness lifecycle.
Requires verification of backup integrity, covering validation only within recovery scenarios.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Cryptographic controls mandate integrity mechanisms whose correct validation directly prevents CWE-354.
Secure coding standards require proper implementation and validation of checksums or MACs.
Security testing can detect missing integrity validation but does not itself implement the control.
Application security requirements include integrity checks on messages and data, mitigating improper validation.
Network security policies may require integrity protection on transit data, indirectly addressing the weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).
Oracle Linux 8 (1 rule)
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. via CWE-354
Oracle Linux 9 (1 rule)
- V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. via CWE-354
RHEL 7 (1 rule)
- V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. via CWE-354