NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-45022: go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git

highCVSS 4.0 7.0GHSA-389r-gv7p-r3rp

Impact go-git may parse malformed Git objects in a way that differs from upstream Git. When commit or tag objects contain ambiguous or malformed headers, go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.

Published May 11, 2026 · Updated Jun 8, 2026

Affected packages

github.com/go-git/go-git/v6

Ecosystem
Go
Affected
>= 6.0.0-alpha.1, <= 6.0.0-alpha.2
Fixed in
6.0.0-alpha.3
Check
go list -m github.com/go-git/go-git/v6

github.com/go-git/go-git/v5

Ecosystem
Go
Affected
< 5.19.0
Fixed in
5.19.0
Check
go list -m github.com/go-git/go-git/v5

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

go-git may parse malformed Git objects in a way that differs from upstream Git. When commit or tag objects contain ambiguous or malformed headers, go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.

Additionally, go-git’s commit signing and verification logic operates over commit data reconstructed from go-git’s parsed representation rather than the original raw object bytes. As a result, go-git may sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository.

This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed.

Patches

Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported go-git version.

Credit

Thanks to @bugbunny-research (https://bugbunny.ai/) for reporting this to sigstore/gitsign, and to @wlynch, @patzielinski and @adityasaky for coordinating the disclosure with the go-git project. :bow: :1st_place_medal:

Thanks to @wayphinder for reporting this to the go-git project. :bow:

Credited to adityasaky, wlynch, patzielinski, bugbunny-research, wayphinder.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries