# GHSA-w5pp-99ch-qj29: go-git: Malformed Git object data may cause panics or resource exhaustion

> Attackers can cause denial of service in applications using go-git by providing malicious Git object data, requiring local file access or malicious remote interaction.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 May 2026
- **Also known as:** GO-2026-5693

## What is GHSA-w5pp-99ch-qj29?

GHSA-w5pp-99ch-qj29 is a denial of service vulnerability in github.com/go-git/go-git/v5, published on 29 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

### Impact
Several denial-of-service issues were identified in `go-git` when parsing maliciously crafted Git repository data.

An attacker may craft a malicious `.pack`, `.idx` or loose objects that causes an application using an affected version of `go-git` to panic or consume excessive resources.

This can lead to denial of service in applications that use `go-git` to clone, fetch, open, or otherwise process untrusted repositories or Git object data.

Exploitation requires the ability to alter read-only files such as `.pack` or `.idx` from the local repository's `.git/objects/pack/` directory. Alternatively, the user would need to be interacting with a malicious remote server, which is not recommended and exposes users to a broader class of security risks beyond this issue.

### 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.

### Credits
go-git thanks @kodareef5, @AyushParkara and @N0zoM1z0 for reporting this in four separate reports. 🙇

## Which versions are affected by GHSA-w5pp-99ch-qj29?

6 open source packages ship an affected version, including github.com/go-git/go-git/v5 and github.com/go-git/go-git/v6.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/go-git/go-git/v5` | Go | All versions | 5.19.1 |
| `github.com/go-git/go-git/v5` | Go | All versions | 5.19.1 |
| `github.com/go-git/go-git/v5` | Go | All versions | 5.19.1 |
| `github.com/go-git/go-git/v6` | Go | All versions | 6.0.0-alpha.4 |
| `github.com/go-git/go-git/v6` | Go | All versions | 6.0.0-alpha.4 |
| `github.com/go-git/go-git/v6` | Go | All versions | 6.0.0-alpha.4 |

## How do I fix GHSA-w5pp-99ch-qj29?

Upgrade github.com/go-git/go-git/v5 to 5.19.1 or later.

## Is GHSA-w5pp-99ch-qj29 being exploited?

There is no known exploitation of GHSA-w5pp-99ch-qj29 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-w5pp-99ch-qj29 and fix it if it is affected.

What it is: GHSA-w5pp-99ch-qj29 is a denial of service vulnerability in github.com/go-git/go-git/v5, published on 29 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-w5pp-99ch-qj29 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/go-git/go-git/v5 (Go): affected all versions; fixed in 5.19.1
- github.com/go-git/go-git/v5 (Go): affected all versions; fixed in 5.19.1
- github.com/go-git/go-git/v5 (Go): affected all versions; fixed in 5.19.1
- github.com/go-git/go-git/v6 (Go): affected all versions; fixed in 6.0.0-alpha.4
- github.com/go-git/go-git/v6 (Go): affected all versions; fixed in 6.0.0-alpha.4
- github.com/go-git/go-git/v6 (Go): affected all versions; fixed in 6.0.0-alpha.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-w5pp-99ch-qj29/ (Markdown: https://insights.sbomify.com/GHSA-w5pp-99ch-qj29/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-w5pp-99ch-qj29

---
From sbomify Insights: https://insights.sbomify.com/GHSA-w5pp-99ch-qj29/
Summaries are generated and may contain mistakes; the official description above is the record.