fix(deps): update module github.com/go-git/go-git/v5 to v5.18.0 [security]#28
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
fix(deps): update module github.com/go-git/go-git/v5 to v5.18.0 [security]#28renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
7bc6333 to
9fc1974
Compare
bc1cb60 to
9fc1974
Compare
02a0cf3 to
9fc1974
Compare
07bd11f to
9fc1974
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
9fc1974 to
6fa8768
Compare
6fa8768 to
314e251
Compare
314e251 to
1a8efca
Compare
1a8efca to
d9ea1d7
Compare
d9ea1d7 to
f5ba9d6
Compare
f5ba9d6 to
0de011d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.12.0→v5.18.0go-git clients vulnerable to DoS via maliciously crafted Git server replies
CVE-2025-21614 / GHSA-r9px-m959-cxf4 / GO-2025-3367
More information
Details
Impact
A denial of service (DoS) vulnerability was discovered in go-git versions prior to
v5.13. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion ingo-gitclients.This is a
go-gitimplementation issue and does not affect the upstreamgitcli.Patches
Users running versions of
go-gitfromv4and above are recommended to upgrade tov5.13in order to mitigate this vulnerability.Workarounds
In cases where a bump to the latest version of
go-gitis not possible, we recommend limiting its use to only trust-worthy Git servers.Credit
Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
go-git has an Argument Injection via the URL field
CVE-2025-21613 / GHSA-v725-9546-7q7m / GO-2025-3368
More information
Details
Impact
An argument injection vulnerability was discovered in
go-gitversions prior tov5.13.Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the
filetransport protocol is being used, as that is the only protocol that shells out togitbinaries.Affected versions
Users running versions of
go-gitfromv4and above are recommended to upgrade tov5.13in order to mitigate this vulnerability.Workarounds
In cases where a bump to the latest version of
go-gitis not possible, we recommend users to enforce restrict validation rules for values passed in the URL field.Credit
Thanks to @vin01 for responsibly disclosing this vulnerability to us.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:ClearReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Clients vulnerable to DoS via maliciously crafted Git server replies in github.com/go-git/go-git
CVE-2025-21614 / GHSA-r9px-m959-cxf4 / GO-2025-3367
More information
Details
Clients vulnerable to DoS via maliciously crafted Git server replies in github.com/go-git/go-git
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Argument Injection via the URL field in github.com/go-git/go-git
CVE-2025-21613 / GHSA-v725-9546-7q7m / GO-2025-3368
More information
Details
Argument Injection via the URL field in github.com/go-git/go-git
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
go-git improperly verifies data integrity values for .idx and .pack files
CVE-2026-25934 / GHSA-37cx-329c-33x3 / GO-2026-4473
More information
Details
Impact
A vulnerability was discovered in
go-gitwhereby data integrity values for.packand.idxfiles were not properly verified. This resulted ingo-gitpotentially consuming corrupted files, which would likely result in unexpected errors such asobject not found.For context, clients fetch
packfilesfrom 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 bygo-git, or thegitcli, when new.packfiles 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 forssh://). 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 latestv6pseudo-version, in order to mitigate this vulnerability.Workarounds
In case updating to a fixed version of
go-gitis not possible, users can run git fsck from thegitcli to check for data corruption on a given repository.Credit
Thanks @N0zoM1z0 for finding and reporting this issue privately to the
go-gitproject.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Improper verification of data integrity values for .idx and .pack files in github.com/go-git/go-git
CVE-2026-25934 / GHSA-37cx-329c-33x3 / GO-2026-4473
More information
Details
Improper verification of data integrity values for .idx and .pack files in github.com/go-git/go-git
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
go-git missing validation decoding Index v4 files leads to panic
CVE-2026-33762 / GHSA-gm2x-2g9h-ccm8 / GO-2026-4909
More information
Details
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-gitsupports onlyv2andv3) are not vulnerable to this issue.An attacker able to supply a crafted
.git/indexfile 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
.gitdirectory.Patches
Users should upgrade to
v5.17.1, or the latestv6pseudo-version, in order to mitigate this vulnerability.Credit
go-git maintainers thank @kq5y for finding and reporting this issue privately to the
go-gitproject.Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
go-git: Maliciously crafted idx file can cause asymmetric memory consumption
CVE-2026-34165 / GHSA-jhf3-xxhw-2wpp / GO-2026-4910
More information
Details
Impact
A vulnerability has been identified in which a maliciously crafted
.idxfile can cause asymmetric memory consumption, potentially exhausting available memory and resulting in a Denial of Service (DoS) condition.Exploitation requires write access to the local repository's
.gitdirectory, it order to create or alter existing.idxfiles.Patches
Users should upgrade to
v5.17.1, or the latestv6pseudo-version, in order to mitigate this vulnerability.Credit
The go-git maintainers thank @kq5y for finding and reporting this issue privately to the
go-gitproject.Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Missing validation decoding Index v4 files leads to panic in github.com/go-git/go-git
CVE-2026-33762 / GHSA-gm2x-2g9h-ccm8 / GO-2026-4909
More information
Details
Missing validation decoding Index v4 files leads to panic in github.com/go-git/go-git
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Maliciously crafted idx file can cause asymmetric memory consumption in github.com/go-git/go-git
CVE-2026-34165 / GHSA-jhf3-xxhw-2wpp / GO-2026-4910
More information
Details
Maliciously crafted idx file can cause asymmetric memory consumption in github.com/go-git/go-git
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
go-git: Credential leak via cross-host redirect in smart HTTP transport
GHSA-3xc5-wrhm-f963
More information
Details
Impact
go-gitmay leak HTTP authentication credentials when following redirects during smart-HTTP clone and fetch operations.If a remote repository responds to the initial
/info/refsrequest with a redirect to a different host, go-git updates the session endpoint to the redirected location and reuses the original authentication for subsequent requests. This can result in the credentials (e.g. Authorization headers) being sent to an unintended host.An attacker controlling or influencing the redirect target can capture these credentials and potentially reuse them to access the victim’s repositories or other resources, depending on the scope of the credential.
Clients using
go-gitexclusively with trusted remotes (for example, GitHub or GitLab), and over a secure HTTPS connection, are not affected by this issue. The risk arises when interacting with untrusted or misconfigured Git servers, or when using unsecured HTTP connections, which is not recommended. Such configurations also expose clients to a broader class of security risks beyond this issue, including credential interception and tampering of repository data.Patches
Users should upgrade to
v5.18.0, orv6.0.0-alpha.2, in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supportedgo-gitversion.The patched versions add support for configuring followRedirects. In line with upstream behaviour, the default is now
initial, while users can opt intoFollowRedirectsorNoFollowRedirectsprogrammatically.Credit
Thanks to the 3 separate reports from @celinke97, @N0zoM1z0 and @AyushParkara. Thanks for finding and reporting this issue privately to the
go-gitproject. 🙇Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
go-git/go-git (github.com/go-git/go-git/v5)
v5.18.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.17.2...v5.18.0
v5.17.2Compare Source
What's Changed
v5.17.1. Thanks @pskrbasu for reporting it. 🙇Full Changelog: go-git/go-git@v5.17.1...v5.17.2
v5.17.1Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.17.0...v5.17.1
v5.17.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.5...v5.17.0
v5.16.5Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.4...v5.16.5
v5.16.4Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.3...v5.16.4
v5.16.3Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.2...v5.16.3
v5.16.2Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.1...v5.16.2
v5.16.1Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.16.0...v5.16.1
v5.16.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.15.0...v5.16.0
v5.15.0Compare Source
What's Changed
releases/v5.xby @Javier-varez in #1482Full Changelog: go-git/go-git@v5.14.0...v5.15.0
v5.14.0Compare Source
What's Changed
golang.org/x/crypto@v0.35.0which 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
v5.13.2Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.13.1...v5.13.2
v5.13.1Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.13.0...v5.13.1
v5.13.0Compare Source
What's Changed
git clean -xflag. by @msuozzo in #995git clean -xflag." by @pjbgf in #1129Untrackedwhile it is committed by @rodrigocam in #1023New Contributors
Full Changelog: go-git/go-git@v5.12.0...v5.13.0
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.