Skip to content
This repository was archived by the owner on Feb 13, 2026. It is now read-only.

housekeeping: Update module github.com/go-git/go-git/v5 to v5.13.0 [SECURITY]#3253

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/go-github.com-go-git-go-git-v5-vulnerability
Closed

housekeeping: Update module github.com/go-git/go-git/v5 to v5.13.0 [SECURITY]#3253
renovate[bot] wants to merge 1 commit intomainfrom
renovate/go-github.com-go-git-go-git-v5-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 19, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-git/go-git/v5 v5.5.2 -> v5.13.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-49569

Impact

A path traversal vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to create and amend files across the filesystem. In the worse case scenario, remote code execution could be achieved.

Applications are only affected if they are using the ChrootOS, which is the default when using "Plain" versions of Open and Clone funcs (e.g. PlainClone). Applications using BoundOS or in-memory filesystems are not affected by this issue.
This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is not possible in a timely manner, we recommend limiting its use to only trust-worthy Git servers.

Credit

Thanks to Ionut Lalu for responsibly disclosing this vulnerability to us.

CVE-2023-49568

Impact

A denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.11. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients.

Applications using only the in-memory filesystem supported by go-git are not affected by this vulnerability.
This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.11 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is 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.

References

CVE-2025-21613

Impact

An argument injection vulnerability was discovered in go-git versions prior to v5.13.

Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the file transport protocol is being used, as that is the only protocol that shells out to git binaries.

Affected versions

Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is 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.

CVE-2025-21614

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 in go-git clients.

This is a go-git implementation issue and does not affect the upstream git cli.

Patches

Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.

Workarounds

In cases where a bump to the latest version of go-git is 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.


Release Notes

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

v5.13.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.12.0...v5.13.0

v5.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.11.0...v5.12.0

v5.11.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.10.1...v5.11.0

v5.10.1

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.10.0...v5.10.1

v5.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.9.0...v5.10.0

v5.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.8.1...v5.9.0

v5.8.1

Compare Source

What's Changed

Full Changelog: go-git/go-git@v5.8.0...v5.8.1

v5.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-git/go-git@v5.7.0...v5.7.1

v5.7.0

Compare Source

What's Changed


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 renovate bot requested a review from a team as a code owner March 19, 2025 15:43
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Mar 19, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Mar 19, 2025

ℹ Artifact update notice

File name: backend/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):

  • 11 additional dependencies were updated

Details:

Package Change
github.com/go-git/go-billy/v5 v5.5.0 -> v5.6.0
github.com/ProtonMail/go-crypto v0.0.0-20230217124315-7d5c6f04bbb8 -> v1.1.3
github.com/cloudflare/circl v1.3.3 -> v1.3.7
github.com/cyphar/filepath-securejoin v0.2.4 -> v0.2.5
github.com/go-git/gcfg v1.5.0 -> v1.5.1-0.20230307220236-3a3c6141e376
github.com/pjbgf/sha1cd v0.2.4-0.20230130103033-0066bacacbf6 -> v0.3.0
github.com/sergi/go-diff v1.1.0 -> v1.3.2-0.20230802210424-5b0b94c5c0d3
github.com/skeema/knownhosts v1.1.0 -> v1.3.0
golang.org/x/exp v0.0.0-20231127185646-65229373498e -> v0.0.0-20240719175910-8a7402abbf56
golang.org/x/mod v0.17.0 -> v0.19.0
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.23.0

@renovate renovate bot force-pushed the renovate/go-github.com-go-git-go-git-v5-vulnerability branch from 8ab6796 to 6283987 Compare March 19, 2025 15:47
@github-actions
Copy link

This PR has been marked as stale after 7 or more days of inactivity. Please have a maintainer add the on hold label if this PR should remain open. If there is no further activity or the on hold label is not added, this PR will be closed in 3 days.

@github-actions github-actions bot added the stale Issue hasn't had activity in awhile label Mar 27, 2025
@github-actions github-actions bot closed this Mar 31, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Mar 31, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v5.13.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/go-github.com-go-git-go-git-v5-vulnerability branch March 31, 2025 15:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file stale Issue hasn't had activity in awhile

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants