CVE-2026-25934: go-git improperly verifies data integrity values for .idx and .pack files
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: go-git go-git 5.16.5.
Low priority for now. Upgrade to go-git go-git 5.16.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
go-git is a highly extensible git implementation library written in pure Go. Prior to 5.16.5, a vulnerability was discovered in go-git whereby data integrity values for .pack and .idx files were not properly verified. This resulted in go-git potentially consuming corrupted files, which would likely result in unexpected errors such as object not found. For context, clients fetch packfiles from upstream Git servers. Those files contain a checksum of their contents, so that clients can perform integrity checks before consuming it. The pack indexes (.idx) are generated locally by go-git, or the git cli, when new .pack files are received and processed. The integrity checks for both files were not being verified correctly. This vulnerability is fixed in 5.16.5.
- Published
- Feb 9, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-354
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.3
- CNA · GitHub_M
- 4.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| go-git project | go-git | cpe:2.3:a:go-git_project:go-git |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- go-git project go-gitbefore 5.16.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
go-git go-git
- < 5.16.5affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | golang-github-go-git-go-git | from 0 | — |
| Debian:14 | golang-github-go-git-go-git | before 5.17.0-1 | 5.17.0-1 |
| Go | github.com/go-git/go-git | from 0 | — |
| Go | github.com/go-git/go-git/v4 | from 0 | — |
| Go | github.com/go-git/go-git/v5 | before 5.16.5 | 5.16.5 |
| openSUSE:Leap 15.6 | terraform-provider-local | before 2.0.0-150200.6.8.1 | 2.0.0-150200.6.8.1 |
| openSUSE:Leap 15.6 | terraform-provider-null | before 3.0.0-150200.6.12.1 | 3.0.0-150200.6.12.1 |
| openSUSE:Leap 15.6 | terraform-provider-random | before 3.0.0-150200.6.6.2 | 3.0.0-150200.6.6.2 |
| openSUSE:Leap 15.6 | terraform-provider-tls | before 3.0.0-150200.5.6.2 | 3.0.0-150200.5.6.2 |
| openSUSE:Leap 16.0 | amazon-ssm-agent | before 3.3.4624.0-160000.1.1 | 3.3.4624.0-160000.1.1 |
| openSUSE:Tumbleweed | alloy | before 1.15.1-1.1 | 1.15.1-1.1 |
| openSUSE:Tumbleweed | amazon-ssm-agent | before 3.3.5226.0-1.1 | 3.3.5226.0-1.1 |
| openSUSE:Tumbleweed | trivy | before 0.70.0-1.1 | 0.70.0-1.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | alloy | before 1.16.1-150700.15.20.1 | 1.16.1-150700.15.20.1 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | amazon-ssm-agent | before 3.3.4624.0-4.49.1 | 3.3.4624.0-4.49.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | amazon-ssm-agent | before 3.3.4624.0-150000.5.37.1 | 3.3.4624.0-150000.5.37.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-aws | before 3.11.0-150200.6.18.1 | 3.11.0-150200.6.18.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-azurerm | before 2.32.0-150200.6.12.1 | 2.32.0-150200.6.12.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-external | before 2.0.0-150200.6.12.1 | 2.0.0-150200.6.12.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-google | before 3.43.0-150200.6.12.1 | 3.43.0-150200.6.12.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-helm | before 2.9.0-150200.6.23.1 | 2.9.0-150200.6.23.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-kubernetes | before 1.13.2-150200.6.12.1 | 1.13.2-150200.6.12.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-local | before 2.0.0-150200.6.17.1 | 2.0.0-150200.6.17.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | terraform-provider-local | before 2.0.0-150200.6.8.1 | 2.0.0-150200.6.8.1 |
+7
Same product
go-git project: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-49569Maliciously crafted Git server replies can lead to path traversal and RCE on go-git clients39Monitor
- CVE-2025-21613go-git has an Argument Injection via the URL field36Monitor
- CVE-2025-21614go-git clients vulnerable to DoS via maliciously crafted Git server replies30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-49568Jan 12, 2024 · Maliciously crafted Git server replies can cause DoS on go-git clients30Monitor
- Later →CVE-2026-33762Mar 31, 2026 · go-git: Missing validation decoding Index v4 files leads to panic11Monitor
- Later →CVE-2026-34165Mar 31, 2026 · go-git: Maliciously crafted idx file can cause asymmetric memory consumption20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| go-git go-git | 5.16.5 · description | Vendor (CNA) |
| debian:golang-github-go-git-go-git | 5.17.0-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/go-git/go-git/v5 | 5.16.5 | Package registry (OSV) |
| opensuse:alloy | 1.15.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:amazon-ssm-agent | 3.3.5226.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:terraform-provider-local | 2.0.0-150200.6.8.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:terraform-provider-null | 3.0.0-150200.6.12.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:terraform-provider-random | 3.0.0-150200.6.6.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:terraform-provider-tls | 3.0.0-150200.5.6.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:trivy | 0.70.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:alloy | 1.16.1-150700.15.20.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:amazon-ssm-agent | 3.3.4624.0-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:terraform-provider-aws | 3.11.0-150200.6.18.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-azurerm | 2.32.0-150200.6.12.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-external | 2.0.0-150200.6.12.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-google | 3.43.0-150200.6.12.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-helm | 2.9.0-150200.6.23.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-kubernetes | 1.13.2-150200.6.12.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-local | 2.0.0-150200.6.8.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-null | 3.0.0-150200.6.12.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-random | 3.0.0-150200.6.6.2 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:terraform-provider-tls | 3.0.0-150200.5.6.2 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-354 · Improper Validation of Integrity Check ValueCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.