CVE-2026-33762 | go-git: Missing validation decoding Index v4 files leads to panic

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 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.

Published: 2026-03-31 Last update: 2026-04-02 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-33762 is rated Low Risk (11.9/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-33762

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-01 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-33762

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.8 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.3 1.4 [email protected]

Weakness enumeration for CVE-2026-33762

GitHub Security Advisory for CVE-2026-33762

GHSA-gm2x-2g9h-ccm8 · Severity: low · Ecosystem: go — go-git missing validation decoding Index v4 files leads to panic

OS Trackers for CVE-2026-33762

vendor priority summary link
debian not yet assigned CVE-2026-33762 not yet assigned priority: Debian including 1 source packages (golang-github-go-git-go-git), 4 status rows across 4 suites (bookworm, forky, sid, trixie): open 2, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-33762
redhat low — https://access.redhat.com/security/cve/CVE-2026-33762
ubuntu medium CVE-2026-33762 medium priority: Ubuntu including 1 source packages (golang-github-go-git-go-git), 4 status rows across 4 suites (jammy, noble, questing, upstream): needs-triage 4. https://ubuntu.com/security/CVE-2026-33762

Affected software / configurations for CVE-2026-33762

Vendor Product Version Raw CPE
go-git_project go-git < 5.17.1 cpe:2.3:a:go-git_project:go-git:*:*:*:*:*:go:*:*

References for CVE-2026-33762

cvelogic Threat Intelligence