Skip to content

← Actionable
Medium, CVSS 5.4

go-git: Crafted repositories may modify main and submodule .git directories

CVE-2026-45571GHSA-crhj-59gh-8x96

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

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

    Affected
    <= 6.0.0-alpha.3
    Fixed in
    6.0.0-alpha.4
  • Go github.com/go-git/go-git/v5

    Affected
    <= 5.19.0
    Fixed in
    5.19.1
  • Go github.com/go-git/go-git

    Affected
    <= 44.7.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
EPSS
  • CVE-2026-45571: 0.30% estimated exploitation activity in the next 30 days; percentile 22.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact A path validation issue in go-git could allow crafted repository data to affect files outside the intended checkout target, including the repository's .git directory. These validations were introduced in upstream Git years ago, so the vulnerability arose from go-git drifting from those checks. Some attack vectors were platform-specific: certain payloads affected only Windows users, others affected only macOS users, and some applied across all supported platforms. Using non-descendant go-billy filesystem instances, or different filesystem types, for the Storer and Worktree may provide some isolation against .git directory manipulation. For example, users that store the .git directory through memfs while using osfs for the worktree are not affected by this vulnerability in the main repository, because repository metadata is not materialized inside the worktree filesystem. However, this isolation does not necessarily apply when the repository contains submodules, since submodule…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-crhj-59gh-8x96

Agent brief

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

# Patch Next advisory brief: CVE-2026-45571

Advisory: go-git: Crafted repositories may modify main and submodule .git directories
IDs: CVE-2026-45571, GHSA-crhj-59gh-8x96
Record: https://patchnext.com/advisories/cve-2026-45571 (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: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/go-git/go-git/v6 6.0.0-alpha.4; github.com/go-git/go-git/v5 5.19.1. 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.3; fixed in 6.0.0-alpha.4
- Go github.com/go-git/go-git/v5: affected <= 5.19.0; fixed in 5.19.1
- Go github.com/go-git/go-git: affected <= 44.7.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.
- Go github.com/go-git/go-git: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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, github.com/go-git/go-git.
- 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-crhj-59gh-8x96 (GitHub-reviewed advisory GHSA-crhj-59gh-8x96 lists affected ranges: Go github.com/go-git/go-git/v5 >=0 =0 =0 <=44.7.0)

Commands are suggestions: review each one before running it.

Loading voting…