fix(deps): update module github.com/go-git/go-git/v5 to v5.17.1 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/go-git/go-git/v5	v5.13.2 → v5.17.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2026-25934

Impact

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.

Note that the lack of verification of the packfile checksum has no impact on the trust relationship between the client and server, which is enforced based on the protocol being used (e.g. TLS in the case of https:// or known hosts for ssh://). In other words, the packfile checksum verification does not provide any security benefits when connecting to a malicious or compromised Git server.

Patches

Users should upgrade to v5.16.5, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Workarounds

In case updating to a fixed version of go-git is not possible, users can run git fsck from the git cli to check for data corruption on a given repository.

Credit

Thanks @​N0zoM1z0 for finding and reporting this issue privately to the go-git project.

CVE-2026-33762

Impact

go-git’s index decoder for format version 4 fails to validate the path name prefix length before applying it to the previously decoded path name. A maliciously crafted index file can trigger an out-of-bounds slice operation, resulting in a runtime panic during normal index parsing.

This issue only affects Git index format version 4. Earlier formats (go-git supports only v2 and v3) are not vulnerable to this issue.

An attacker able to supply a crafted .git/index file can cause applications using go-git to panic while reading the index. If the application does not recover from panics, this results in process termination, leading to a denial-of-service (DoS) condition.

Exploitation requires the ability to modify or inject a Git index file within the local repository in disk. This typically implies write access to the .git directory.

Patches

Users should upgrade to v5.17.1, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Credit

go-git maintainers thank @​kq5y for finding and reporting this issue privately to the go-git project.

---

Release Notes

go-git/go-git (github.com/go-git/go-git/v5)

v5.17.1

Compare Source

What's Changed

• build: Update module github.com/cloudflare/circl to v1.6.3 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1930
• [v5] plumbing: format/index, Improve v4 entry name validation by @​pjbgf in #​1935
• [v5] plumbing: format/idxfile, Fix version and fanout checks by @​pjbgf in #​1937

Full Changelog: go-git/go-git@v5.17.0...v5.17.1

v5.17.0

Compare Source

What's Changed

• build: Update module github.com/go-git/go-git/v5 to v5.16.5 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1839
• git: worktree, optimize infiles function for very large repos by @​k-anshul in #​1853
• git: Add strict checks for supported extensions by @​pjbgf in #​1861
• backport, git: Improve Status() speed with new index.ModTime check by @​cedric-appdirect in #​1862
• storage: filesystem, Avoid overwriting loose obj files by @​pjbgf in #​1864

Full Changelog: go-git/go-git@v5.16.5...v5.17.0

v5.16.5

Compare Source

What's Changed

• build: Update module golang.org/x/crypto to v0.45.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1744
• build: Bump Go test versions to 1.23-1.25 (v5) by @​pjbgf in #​1746
• [v5] git: worktree, Don't delete local untracked files when resetting worktree by @​Ch00k in #​1800
• Expand packfile checks by @​pjbgf in #​1836

Full Changelog: go-git/go-git@v5.16.4...v5.16.5

v5.16.4

Compare Source

What's Changed

• backport plumbing: format/idxfile, prevent panic by @​swills in #​1732
• [backport] build: test, Fix build on Windows. by @​pjbgf in #​1734
• build: Update module golang.org/x/net to v0.38.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1742
• build: Update module github.com/cloudflare/circl to v1.6.1 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1741
• build: Update module github.com/go-git/go-git/v5 to v5.13.0 [SECURITY] (releases/v5.x) by @​go-git-renovate[bot] in #​1743

Full Changelog: go-git/go-git@v5.16.3...v5.16.4

v5.16.3

Compare Source

What's Changed

• internal: Expand regex to fix build [5.x] by @​baloo in #​1644
• build: raise timeouts for windows CI tests and disable CIFuzz [5.x] by @​baloo in #​1646
• plumbing: support commits extra headers, support jujutsu signed commit [5.x] by @​baloo in #​1633

Full Changelog: go-git/go-git@v5.16.2...v5.16.3

v5.16.2

Compare Source

What's Changed

• utils: fix diff so subpaths work for sparse checkouts, fixes 1455 to releases/v5.x by @​kane8n in #​1567

Full Changelog: go-git/go-git@v5.16.1...v5.16.2

v5.16.1

Compare Source

What's Changed

• utils: merkletrie, Fix diff on sparse-checkout index. Fixes #​1406 to releases/v5.x by @​kane8n in #​1561

New Contributors

• @​kane8n made their first contribution in #​1561

Full Changelog: go-git/go-git@v5.16.0...v5.16.1

v5.16.0

Compare Source

What's Changed

• [v5] plumbing: support mTLS for HTTPS protocol by @​hiddeco in #​1510
• v5: plumbing: transport, Reintroduce SetHostKeyCallback. Fix #​1514 by @​pjbgf in #​1515

Full Changelog: go-git/go-git@v5.15.0...v5.16.0

v5.15.0

Compare Source

What's Changed

• plumbing: add cert auth support to releases/v5.x by @​Javier-varez in #​1482
• v5: Bump dependencies by @​pjbgf in #​1505

Full Changelog: go-git/go-git@v5.14.0...v5.15.0

v5.14.0

Compare Source

What's Changed

• v5: Bump Go and dependencies to mitigate GO-2025-3487 by @​pjbgf in #​1436

⚠️ Note that this version requires Go 1.23, due to the bump to golang.org/x/crypto@v0.35.0 which mitigates the CVE above. User's that can't bump to Go 1.23 will need to remain on the previous v5.13.x release.

Full Changelog: go-git/go-git@v5.13.2...v5.14.0

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 6 additional dependencies were updated

Details:

Package	Change
github.com/ProtonMail/go-crypto	v1.1.5 -> v1.1.6
github.com/cloudflare/circl	v1.6.1 -> v1.6.3
github.com/cyphar/filepath-securejoin	v0.3.6 -> v0.4.1
github.com/go-git/go-billy/v5	v5.6.2 -> v5.8.0
github.com/golang/groupcache	v0.0.0-20210331224755-41bb18bfe9da -> v0.0.0-20241129210726-2c02b8208cf8
github.com/skeema/knownhosts	v1.3.0 -> v1.3.1

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cursor]

No high-confidence vulnerabilities found.

Security-focused review of the diff shows only dependency metadata changes in go.mod and go.sum:

• github.com/go-git/go-git/v5 upgraded v5.13.2 -> v5.16.5 (the stated security fix train)
• Transitive updates are consistent with that upgrade (github.com/ProtonMail/go-crypto, github.com/cyphar/filepath-securejoin, github.com/golang/groupcache, github.com/skeema/knownhosts)
• No application code changes were introduced, so no new direct injection/auth/logging/SSRF/XSS/request-forgery surfaces are visible in this PR.

Residual risk / validation:

• This assessment assumes upstream module releases are trusted and checksums are correctly validated by the Go module system.
• Recommend running normal CI + dependency/vuln scanning after merge to catch any behavioral regressions from transitive upgrades.

---