fix(security/HIGH): Update module github.com/go-git/go-git/v5 to v5.19.0 [SECURITY]#6229
Closed
renovate-sh-app[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: collector/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: extension/alloyengine/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Contributor
🔍 Dependency Reviewgithub.zerozr99.workers.dev/go-git/go-git/v5 v5.18.0 -> v5.19.0 — ✅ SafeSummary
References
Notes
Suggested actions
github.com/go-git/go-billy/v5 v5.8.0 -> v5.9.0 — ✅ SafeSummary
References
Suggested actions
github.com/pjbgf/sha1cd v0.3.2 -> v0.6.0 — ✅ SafeSummary
References
Suggested actions
github.com/cyphar/filepath-securejoin v0.6.0 -> v0.6.1 — ✅ SafeSummary
References
Suggested actions
Notes
|
renovate-sh-app
Bot
force-pushed
the
renovate/go-github.zerozr99.workers.dev-go-git-go-git-v5-vulnerability
branch
10 times, most recently
from
5b1256d to
51bcf89
Compare
renovate-sh-app
Bot
changed the title
auto-merge was automatically disabled
May 14, 2026 09:17
Pull request was closed
renovate-sh-app
Bot
deleted the
renovate/go-github.zerozr99.workers.dev-go-git-go-git-v5-vulnerability
branch
renovate-sh-app
Bot
changed the title
renovate-sh-app
Bot
force-pushed
the
renovate/go-github.zerozr99.workers.dev-go-git-go-git-v5-vulnerability
branch
2 times, most recently
from
51bcf89 to
224e794
Compare
renovate-sh-app
Bot
changed the title
…9.0 [SECURITY] | datasource | package | from | to | | ---------- | --------------------------- | ------- | ------- | | go | github.com/go-git/go-git/v5 | v5.18.0 | v5.19.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
renovate-sh-app
Bot
changed the title
renovate-sh-app
Bot
force-pushed
the
renovate/go-github.zerozr99.workers.dev-go-git-go-git-v5-vulnerability
branch
2 times, most recently
from
224e794 to
3232896
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
1 participant
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.18.0→v5.19.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
CVE-2026-45022 / GHSA-389r-gv7p-r3rp
More information
Details
Impact
go-gitmay parse malformed Git objects in a way that differs from upstream Git. Whencommitortagobjects contain ambiguous or malformed headers,go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.Additionally,
go-git’s commit signing and verification logic operates over commit data reconstructed fromgo-git’s parsed representation rather than the original raw object bytes. As a result,go-gitmay sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository.This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed.
Patches
Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported
go-gitversion.Credit
Thanks to @bugbunny-research (https://bugbunny.ai/) for reporting this to
sigstore/gitsign, and to @wlynch, @patzielinski and @adityasaky for coordinating the disclosure with thego-gitproject. 🙇 🥇Thanks to @wayphinder for reporting this to the
go-gitproject. 🙇Severity
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git
CVE-2026-45022 / GHSA-389r-gv7p-r3rp
More information
Details
Impact
go-gitmay parse malformed Git objects in a way that differs from upstream Git. Whencommitortagobjects contain ambiguous or malformed headers,go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.Additionally,
go-git’s commit signing and verification logic operates over commit data reconstructed fromgo-git’s parsed representation rather than the original raw object bytes. As a result,go-gitmay sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository.This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed.
Patches
Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported
go-gitversion.Credit
Thanks to @bugbunny-research (https://bugbunny.ai/) for reporting this to
sigstore/gitsign, and to @wlynch, @patzielinski and @adityasaky for coordinating the disclosure with thego-gitproject. 🙇 🥇Thanks to @wayphinder for reporting this to the
go-gitproject. 🙇Severity
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA: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.19.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.18.0...v5.19.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.