go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
go-git is an extensible git implementation library written in pure Go. Prior to 5.19.0 and 6.0.0-alpha.3, 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. This vulnerability is fixed in 5.19.0 and 6.0.0-alpha.3.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-45022
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 19:11 UTC · Revision 1
Source evidence
go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
core-osv · Original sourcePublished 27 May 2026, 14:54 UTC
go-git is an extensible git implementation library written in pure Go. Prior to 5.19.0 and 6.0.0-alpha.3, 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. This vulnerability is fixed in 5.19.0 and 6.0.0-alpha.3.
osv:CVE-2026-45022
Complete source record
{
"id": "6ef54c606421a5cbe0e7bad48b6ea07a968222e8354abfedc2a7bebded9b5107",
"url": "https://osv.dev/vulnerability/CVE-2026-45022",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "go-git: Improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git",
"summary": "go-git is an extensible git implementation library written in pure Go. Prior to 5.19.0 and 6.0.0-alpha.3, 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. This vulnerability is fixed in 5.19.0 and 6.0.0-alpha.3.",
"evidence": "osv:CVE-2026-45022",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-45022",
"aliases": [
"CVE-2026-45022",
"GHSA-389r-gv7p-r3rp",
"GO-2026-5074"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/go-git/go-git",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "bc930f4cbe095a3e1d49273655f73fcef7d41a42"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:go-git_project:go-git:*:*:*:*:*:go:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "5.19.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v5.18.0",
"v5.17.2",
"v5.17.1",
"v5.17.0",
"v5.16.5",
"v5.16.4",
"v5.16.3",
"v5.16.2",
"v5.16.1",
"v5.16.0",
"v5.15.0",
"v5.14.0",
"v5.13.2",
"v5.13.1",
"v5.13.0",
"v5.12.0",
"v5.11.0",
"v5.10.1",
"v5.9.0",
"v5.10.0",
"v5.8.1",
"v5.8.0",
"v5.7.0",
"v5.6.1",
"v5.5.2",
"v5.6.0",
"v5.5.1",
"v5.5.0",
"v5.4.2",
"v5.4.1",
"v5.4.0",
"v5.3.0",
"v5.2.0",
"v5.1.0",
"v5.0.0",
"v4.13.1",
"v4.13.0",
"v4.12.0",
"v4.11.0",
"v4.10.0",
"v4.9.1",
"v4.7.1",
"v4.9.0",
"v4.8.1",
"v4.8.0",
"v4.7.0",
"v4.6.0",
"v4.5.0",
"v4.4.1",
"v4.4.0",
"v4.3.1",
"v4.3.0",
"v4.2.1",
"v4.2.0",
"v4.1.1",
"v4.1.0",
"v4.0.0",
"v4.0.0-rc15",
"v4.0.0-rc14",
"v4.0.0-rc13",
"v4.0.0-rc12",
"v4.0.0-rc11",
"v4.0.0-rc10",
"v4.0.0-rc9",
"v4.0.0-rc8",
"v4.0.0-rc7",
"v4.0.0-rc6",
"v4.0.0-rc5",
"v4.0.0-rc4",
"v4.0.0-rc3",
"v4.0.0-rc2",
"v4.0.0-rc1",
"v3.1.1",
"v3.1.0",
"v3.0.4",
"v3.0.3",
"v3.0.2",
"v3.0.1",
"v3.0.0",
"v2.2.0",
"v2.1.3",
"v2.1.2",
"v2.1.1",
"v2.1.0",
"v2.0.0",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45022.json"
}
}
],
"modified": "2026-10-28T02:30:47.926930054Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45022.json",
"https://github.com/go-git/go-git/security/advisories/GHSA-389r-gv7p-r3rp",
"https://nvd.nist.gov/vuln/detail/CVE-2026-45022"
],
"provider_metadata": {
"cwe_ids": [
"CWE-180",
"CWE-345"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45022.json"
}
},
"related_cves": [
{
"value": "CVE-2026-45022",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 515948,
"published_at": "2026-05-27T14:54:47.872+00:00"
}