Update vulnerable dependencies [SECURITY]#490
Open
pulumi-renovate[bot] wants to merge 1 commit intomainfrom
Open
Update vulnerable dependencies [SECURITY]#490pulumi-renovate[bot] wants to merge 1 commit intomainfrom
pulumi-renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
ℹ Artifact update noticeFile name: provider/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Does the PR have any schema changes?Found 1 breaking change: Functions
New functions:
Maintainer note: consult the runbook for dealing with any breaking changes. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #490 +/- ##
=====================================
Coverage 0.00% 0.00%
=====================================
Files 1 1
Lines 61 61
=====================================
Misses 61 61 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
519a8f9 to
674cd90
Compare
674cd90 to
332f48e
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.17.1->v5.18.0v1.7.9->v1.8.6GitHub Vulnerability Alerts
GHSA-3xc5-wrhm-f963
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. 🙇CVE-2026-4660
HashiCorp's go-getter library up to v1.8.5 may allow arbitrary file reads on the file system during certain git operations through a maliciously crafted URL. This is fixed in go-getter v1.8.6. This vulnerability does not affect the go-getter/v2 branch and package.
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
hashicorp/go-getter (github.com/hashicorp/go-getter)
v1.8.6Compare Source
v1.8.5Compare Source
What's Changed
NOTES:
Binary Distribution Update: To streamline our release process and align with other HashiCorp tools, all release binaries will now be published exclusively to the official HashiCorp release site. We will no longer attach release assets to GitHub Releases.
New Contributors
Full Changelog: hashicorp/go-getter@v1.8.4...v1.8.5
v1.8.4Compare Source
What's Changed
New Contributors
Full Changelog: hashicorp/go-getter@v1.8.3...v1.8.4
v1.8.3Compare Source
What's Changed
New Contributors
Full Changelog: hashicorp/go-getter@v1.8.2...v1.8.3
v1.8.2Compare Source
What's Changed
New Contributors
Full Changelog: hashicorp/go-getter@v1.8.1...v1.8.2
v1.8.1Compare Source
What's Changed
New Contributors
Full Changelog: hashicorp/go-getter@v1.8.0...v1.8.1
v1.8.0What's Changed
New Contributors
Full Changelog: hashicorp/go-getter@v1.7.9...v1.8.0
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - Monday through Friday ( * * * * 1-5 ) (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.