Skip to content

← Actionable
Critical, CVSS 9.8

Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients

CVE-2023-49569GHSA-449p-3h89-pw88

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/v5

    Affected
    >= 5.0.0, < 5.11.0
    Fixed in
    5.11.0
  • Go gopkg.in/src-d/go-git.v4

    Affected
    >= 4.0.0, <= 4.13.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2023-49569: 1.51% estimated exploitation activity in the next 30 days; percentile 74.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 traversal vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved. Applications are only affected if they are using the ChrootOS, which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS or in-memory filesystems are not affected by this issue. This is a go-git implementation issue and does not affect the upstream git cli. Patches Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability. Workarounds In cases where a bump to the latest version of go-git is not possible in a timely manner, we recommend limiting its use to only trust-worthy Git servers. Credit Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

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

    Published from ghsa record GHSA-449p-3h89-pw88

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-2023-49569

Advisory: Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients
IDs: CVE-2023-49569, GHSA-449p-3h89-pw88
Record: https://patchnext.com/advisories/cve-2023-49569 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
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/v5 5.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-git/go-git/v5: affected >= 5.0.0, < 5.11.0; fixed in 5.11.0
- Go gopkg.in/src-d/go-git.v4: affected >= 4.0.0, <= 4.13.1

## Suggested inspection (read-only)
- Go github.com/go-git/go-git/v5: check the installed version with your package manager.
- Go gopkg.in/src-d/go-git.v4: 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/v5, gopkg.in/src-d/go-git.v4.
- 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-449p-3h89-pw88 (GitHub-reviewed advisory GHSA-449p-3h89-pw88 lists affected ranges: Go github.com/go-git/go-git/v5 >=5.0.0 =4.0.0 <=4.13.1)

Commands are suggestions: review each one before running it.

Loading voting…