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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.0 · 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 · score source

EPSS

• CVE-2026-45022: 0.16% estimated exploitation activity in the next 30 days; percentile 5.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

11 May 2026, 14:48 UTC

Last modified by the source

8 Jun 2026, 23:42 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-389r-gv7p-r3rp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45022

Advisory: go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
IDs: CVE-2026-45022, GHSA-389r-gv7p-r3rp
Record: https://patchnext.com/advisories/cve-2026-45022 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/go-git/go-git/v6 6.0.0-alpha.3; github.com/go-git/go-git/v5 5.19.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-git/go-git/v6: affected >= 6.0.0-alpha.1, <= 6.0.0-alpha.2; fixed in 6.0.0-alpha.3
- Go github.com/go-git/go-git/v5: affected < 5.19.0; fixed in 5.19.0

## Suggested inspection (read-only)
- Go github.com/go-git/go-git/v6: check the installed version with your package manager.
- Go github.com/go-git/go-git/v5: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/go-git/go-git/v6, github.com/go-git/go-git/v5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-389r-gv7p-r3rp (GitHub-reviewed advisory GHSA-389r-gv7p-r3rp lists affected ranges: Go github.com/go-git/go-git/v6 >=6.0.0-alpha.1 =0 <5.19.0)

Commands are suggestions: review each one before running it.