CVE-2026-33762
Go-Git Project Go-Git ≤ 5.17.1
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:LSummary
CVE-2026-33762 is a low-severity Improper Validation of Array Index (CWE-129) vulnerability in Go-Git Project Go-Git. Its CVSS base score is 2.8 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 5th 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-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-17443
Vulnerability Data
go-git is an extensible git implementation library written in pure Go. Prior to version 5.17.1, go-git’s index decoder for format version 4 fails to validate the path name prefix length before applying it to the previously decoded path name. A…
more
maliciously crafted index file can trigger an out-of-bounds slice operation, resulting in a runtime panic during normal index parsing. This issue only affects Git index format version 4. Earlier formats (go-git supports only v2 and v3) are not vulnerable to this issue. This issue has been patched in version 5.17.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Malformed Git index v4 triggers OOB slice panic in go-git parser, directly enabling application DoS via exploitation.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of index fields such as path-name prefix length before use in slice operations, eliminating the CWE-129 flaw.
Mandates timely application of the available patch (go-git 5.17.1) that corrects the version-4 decoder.
Enables integrity verification of both the go-git binary and received index files to detect tampering that could trigger the panic.
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.
Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.
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.
Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.
Application security requirements include validation of untrusted input used for indexing or addressing memory structures.
Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.
Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.