# go-git: Maliciously crafted idx file can cause asymmetric memory consumption

Advisory record · `GHSA-jhf3-xxhw-2wpp`

- **Identifiers:** `GHSA-jhf3-xxhw-2wpp` · `CVE-2026-34165` · `GO-2026-4910`
- **State:** Confirmed
- **Severity:** CVSS 5.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-191](https://cwe.mitre.org/data/definitions/191.html) · [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 30 Mar 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 Mar 2026, 17:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/go-git/go-git/v5` (Go): affected `>=5.0.0, <5.17.1`; fixed in `5.17.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> go-git (github.com/go-git/go-git/v5) versions 5.0.0 through 5.17.0 are vulnerable to a maliciously crafted .idx file causing asymmetric memory consumption. An attacker who can write to a local repository's .git directory can create or alter .idx files, potentially exhausting memory and causing a denial of service. Upgrade to go-git v5.17.1 or later v6 release.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.0 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jhf3-xxhw-2wpp)

## Sources

- [GitHub Advisory Database: GHSA-jhf3-xxhw-2wpp](https://github.com/advisories/GHSA-jhf3-xxhw-2wpp)
- [OSV: GHSA-jhf3-xxhw-2wpp](https://osv.dev/vulnerability/GHSA-jhf3-xxhw-2wpp)
- <https://github.com/go-git/go-git/security/advisories/GHSA-jhf3-xxhw-2wpp>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34165>
- <https://github.com/go-git/go-git>
- <https://github.com/go-git/go-git/releases/tag/v5.17.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jhf3-xxhw-2wpp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jhf3-xxhw-2wpp/>. Everything for agents: <https://agentprime.io/llms.txt>.
