Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
479798a
Executing automated changes
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
40eae83
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
a79055b
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
ab87b79
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
a9ad27e
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
6ae4d17
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
30e9164
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
0a164aa
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
0a99433
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
bef3f5e
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
1a39585
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
6dd9b83
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
19b1098
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
d1974e7
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
00feafa
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
61d6443
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
de58070
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
1c6ca3a
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
b77236d
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
d65d6e2
chore: regenerate lockfiles after rebase
dd-octo-sts-6cbbf8[bot] Jun 12, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions test/e2e-framework/go.mod
Original file line number Diff line number Diff line change
Expand Up @@ -134,8 +134,8 @@ require (
github.com/fxamacker/cbor/v2 v2.9.1 // indirect
github.com/go-errors/errors v1.5.1 // indirect
github.com/go-git/gcfg v1.5.1-0.20230307220236-3a3c6141e376 // indirect
github.com/go-git/go-billy/v5 v5.6.2 // indirect
github.com/go-git/go-git/v5 v5.16.5 // indirect
github.com/go-git/go-billy/v5 v5.9.0 // indirect
github.com/go-git/go-git/v5 v5.19.0 // indirect

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the patched release

This security remediation upgrades github.com/go-git/go-git/v5 only to v5.19.0, but the upstream advisory for GHSA-w5pp-99ch-qj29 marks <=5.19.0 as affected and 5.19.1 as the patched version (GHSA-w5pp-99ch-qj29). In any E2E framework path that processes repository data via this transitive dependency, merging this still leaves a known moderate DoS vulnerability for malformed Git objects, so the remediation should target at least v5.19.1.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed patch release

This security remediation pins github.com/go-git/go-git/v5 to v5.19.0, but current advisories still mark versions before v5.19.1 as affected by CVE-2026-45570/CVE-2026-45571 (for SSH repository paths with embedded quotes and crafted repository checkout paths; see https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45570/). As a result, this manifest can continue to be flagged and any E2E/Pulumi path that uses go-git on such repositories remains exposed; please select v5.19.1 instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin go-git to the patched v5.19.1 release

This security remediation now pins github.com/go-git/go-git/v5 at v5.19.0, but the newer GitHub advisories GHSA-crhj-59gh-8x96 and GHSA-m7cr-m3pv-hgrp list <=5.19.0 as affected and 5.19.1 as the patched version. In E2E framework paths where the transitive go-git user fetches or checks out attacker-controlled repositories, this still leaves the path-traversal/SSH-quoting issues present and vulnerability scanners will continue to flag the module; please bump to v5.19.1 and refresh go.sum.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the patched 5.19.1 release

This security update leaves github.com/go-git/go-git/v5 at v5.19.0, but CVE-2026-45571 affects go-git versions before 5.19.1 and can let crafted repository data modify files outside the intended checkout target; NVD lists 5.19.1 as the fixed version (https://nvd.nist.gov/vuln/detail/CVE-2026-45571). Since this commit is already changing the module for vulnerability remediation, the e2e-framework module will continue to be flagged until it targets v5.19.1 or newer.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin go-git to the patched release

This security bump stops at v5.19.0, but GitHub advisory GHSA-m7cr-m3pv-hgrp marks all github.com/go-git/go-git/v5 versions <=5.19.0 as affected and 5.19.1 as patched. In e2e jobs that clone over SSH with a repository path containing a single quote against shell-evaluating SSH servers, the framework still carries the escaping vulnerability, so this remediation should target v5.19.1 and update go.sum instead of pinning the last affected version.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the patched release

This dependency update lands on github.com/go-git/go-git/v5 v5.19.0, but the current go-git advisories mark all versions before 5.19.1 as affected by CVE-2026-45570 (SSH transport quoting) and CVE-2026-45571 (crafted repository checkout path validation), with 5.19.1 listed as the fixed version (see NVD/GitLab advisories: https://nvd.nist.gov/vuln/detail/CVE-2026-45570 and https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45571/). Any e2e-framework path that lets Pulumi/go-git clone over SSH or checkout a crafted repo would still use the vulnerable code, so this security bump should target at least v5.19.1 instead of v5.19.0.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to fixed v5.19.1 release

This security update pins go-git at v5.19.0, but GHSA-w5pp-99ch-qj29 marks all versions before v5.19.1 as affected by malformed Git repository data causing panics or excessive resource use. In contexts where the e2e framework/Pulumi stack processes an untrusted or malicious repo/pack/idx, this module can still be flagged as vulnerable, so the remediation should target v5.19.1 on the v5 line instead of stopping at v5.19.0.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade go-git to 5.19.1 to close the advisory

This security bump stops at github.com/go-git/go-git/v5 v5.19.0, but GHSA-w5pp-99ch-qj29 was published before this commit and marks all versions before 5.19.1 as affected; when the E2E framework's transitive go-git path clones/fetches or processes untrusted repository data, crafted pack/idx/loose objects can still cause panic or excessive resource use, so this remediation will continue to be flagged until the module is bumped to v5.19.1 or newer.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed 5.19.1 release

This remediation still pins github.com/go-git/go-git/v5 to v5.19.0, but GHSA-crhj-59gh-8x96 / CVE-2026-45571 marks versions before 5.19.1 as affected. Since this PR is intended to clear go-git vulnerabilities, scanners will continue to report this module and any e2e-framework/Pulumi path that processes a crafted repository remains exposed; please bump to at least v5.19.1 instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin go-git to the fixed patch release

This dependency bump still pins github.com/go-git/go-git/v5 to v5.19.0, but the upstream GitHub advisory GHSA-crhj-59gh-8x96 lists <=5.19.0 as affected and 5.19.1 as the patched version. In contexts where the E2E framework dependency tree is scanned or uses go-git against a crafted repository, this PR will continue to be reported as vulnerable; bump this line to v5.19.1 or newer.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Synchronize the rest of the workspace modules

Because the go_mod_tidy_check job runs dda inv -- -e check-mod-tidy (.gitlab/build/source_test/linux.yml:172-180), and that task first runs go work sync then fails on any go.mod/go.sum diff (tasks/go.py:311-314), bumping only test/e2e-framework leaves the workspace inconsistent. The Go Modules Reference says go work sync syncs the workspace build list back to each workspace module, and go.work includes test/new-e2e and internal/tools; both still require go-git v5.16.5, go-billy v5.6.2, and sha1cd v0.3.2, so this change will make that CI check rewrite those manifests instead of passing.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Upgrade go-git to a patched version

This security remediation still pins github.com/go-git/go-git/v5 to v5.19.0, but the upstream GHSA-w5pp-99ch-qj29 advisory marks all <=5.19.0 releases as affected and patches the DoS issue in 5.19.1; when this module processes malicious Git repository data, it remains vulnerable, so the dependency should be bumped to v5.19.1 or newer instead of stopping at v5.19.0.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Upgrade go-git to the fixed 5.19.1 release

For this security-remediation update, pinning github.com/go-git/go-git/v5 to v5.19.0 still leaves this module in the affected range for recently published go-git advisories fixed in v5.19.1 (including malformed object/pack resource-exhaustion and SSH path quoting issues). In e2e-framework contexts where Pulumi/go-git fetches repositories or consumes Git object data, dependency scanners will continue to flag this and the vulnerable code remains reachable, so this should move to v5.19.1 or newer instead of stopping at v5.19.0.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to 5.19.1

This security update lands on github.com/go-git/go-git/v5 v5.19.0, but advisories published before this commit mark all go-git versions before 5.19.1 as affected for malformed repository data DoS and SSH path quoting issues, with 5.19.1 as the fixed version (see https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/GHSA-w5pp-99ch-qj29/ and https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45570/). As a result, this vulnerability-remediation commit will still leave test/e2e-framework flagged by dependency scanners and vulnerable if this transitive go-git path is used to process attacker-controlled repositories or SSH paths.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin go-git to the fixed security release

For this vulnerability-remediation update, v5.19.0 is still in the vulnerable range for the current go-git advisories fixed in v5.19.1 (for example the crafted-repository path validation issue and SSH repository-path quoting issue). As a result, this module will continue to be flagged by security scanners and remains exposed in contexts where the e2e framework or its transitive tooling processes untrusted git repositories; please bump github.com/go-git/go-git/v5 to v5.19.1 or newer and refresh go.sum.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git past the remaining SSH CVE

This security remediation pins go-git to v5.19.0, but that version is still in the affected range for CVE-2026-45570; the fix is v5.19.1 or newer. In any e2e-framework path that reaches go-git's SSH transport with a repository path containing a single quote, the command escaping issue remains, and vulnerability scanners will continue to report the dependency after this PR.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed 5.19.1 release

This pins github.com/go-git/go-git/v5 to v5.19.0, but the currently published advisory GHSA-w5pp-99ch-qj29 marks all versions before 5.19.1 as affected and says to upgrade to 5.19.1 or above (https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/GHSA-w5pp-99ch-qj29/). For e2e-framework paths that clone/fetch/open repositories through this transitive dependency, a malicious remote or crafted local Git object data can still cause panic/resource exhaustion, so this security remediation will remain vulnerable and scanner-visible until the version is raised to 5.19.1+.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the patched release

This security update still pins github.com/go-git/go-git/v5 to a vulnerable release: GitHub advisory GHSA-w5pp-99ch-qj29, published May 18, 2026, lists affected versions as <=5.19.0 and the patched version as 5.19.1. In contexts where the e2e framework or its Pulumi dependencies clone/fetch/open repositories from a malicious remote or crafted local Git objects, this leaves the DoS/resource-exhaustion issue unresolved and dependency scanning will continue to flag the module, so this should be bumped to v5.19.1 instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade go-git to the patched release

This dependency bump still pins github.com/go-git/go-git/v5 to v5.19.0, but the current advisories for CVE-2026-45570 and CVE-2026-45571 mark all versions before 5.19.1 as affected and recommend upgrading to 5.19.1 or above (see https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45570/ and https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45571/). In contexts where the e2e framework or Pulumi stack handles attacker-controlled Git URLs/repositories, this leaves the module vulnerable and will continue to fail dependency scanning despite the security-update commit.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade go-git to the fixed 5.19.1 release

This security bump stops at github.com/go-git/go-git/v5 v5.19.0, but the current go-git advisories list all versions before 5.19.1 as affected (for example GHSA-w5pp-99ch-qj29: https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/GHSA-w5pp-99ch-qj29/). As a result, dependency scanning for test/e2e-framework will still report this module as vulnerable, and any e2e code path that processes a malicious repository through go-git remains exposed; pin the dependency to 5.19.1 or newer instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the patched v5.19.1 release

This security update still pins github.com/go-git/go-git/v5 to v5.19.0, but GitHub advisory GHSA-w5pp-99ch-qj29 lists <=5.19.0 as affected and 5.19.1 as the patched version (GHSA-w5pp-99ch-qj29). When the e2e framework's dependency graph processes untrusted Git object data through go-git, the module remains exposed to the crafted-repository DoS that this remediation is meant to clear, and scanners will continue to flag it; please bump to v5.19.1 and regenerate the sums.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to v5.19.1

This security-remediation update pins github.com/go-git/go-git/v5 at v5.19.0, but that version is still covered by current go-git advisories: CVE-2026-45570/GHSA-m7cr-m3pv-hgrp and CVE-2026-45571/GHSA-crhj-59gh-8x96 both affect releases before v5.19.1. Because this module still carries the vulnerable go-git version after the PR, vulnerability scanners and any e2e-framework path that pulls/clones repositories through the transitive Pulumi/go-git stack remain exposed; please bump this dependency to v5.19.1 and refresh go.sum.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git past the vulnerable 5.19.0 release

This security-remediation update pins github.com/go-git/go-git/v5 to v5.19.0, but OSV lists <= 5.19.0 as still affected for GHSA-crhj-59gh-8x96 / CVE-2026-45571 and fixed in 5.19.1 (https://osv.dev/vulnerability/GHSA-crhj-59gh-8x96). In any test/e2e-framework path that reaches go-git on crafted repository data, this keeps the module vulnerable and will also leave vulnerability scanners reporting the dependency after this PR; please upgrade to at least v5.19.1.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed patch release

This security remediation pins github.com/go-git/go-git/v5 to v5.19.0, but that version is still below the fixed release for CVE-2026-45570: the advisory lists all versions before 5.19.1 as affected and says to upgrade to 5.19.1 or above (https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45570/). In contexts where the E2E framework/Pulumi follows attacker-influenced SSH Git URLs with repository paths containing a single quote against a shell-evaluating SSH server, this leaves the dependency update still vulnerable; use v5.19.1 instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git past vulnerable v5.19.0

This security update pins github.com/go-git/go-git/v5 at v5.19.0, but GHSA-w5pp-99ch-qj29, published May 29, 2026, marks all versions before v5.19.1 as affected and recommends upgrading to 5.19.1 or above. In any e2e-framework path that clones, fetches, opens, or otherwise processes malicious Git repository data through go-git, this still leaves the panic/resource-exhaustion DoS that the dependency remediation is meant to clear; please bump to v5.19.1 and refresh the sums.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git past the still-vulnerable release

This security-remediation PR still pins github.com/go-git/go-git/v5 to v5.19.0, but GitHub Advisory GHSA-m7cr-m3pv-hgrp / CVE-2026-45570 lists <= 5.19.0 as affected and 5.19.1 as the patched version. In E2E paths that use go-git over SSH with attacker-influenced repository paths containing a single quote against shell-evaluating SSH servers, this version can still emit unsafe remote exec commands, so the module remains vulnerable and will continue to be flagged; use v5.19.1 or newer instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed 5.19.1 release

This security-remediation change pins go-git to v5.19.0, but that version is still covered by GHSA-w5pp-99ch-qj29: the GitLab advisory lists all versions before 5.19.1 as affected and recommends upgrading to 5.19.1 or above (https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/GHSA-w5pp-99ch-qj29/). In contexts where the e2e framework or Pulumi transitively opens/fetches a malicious repository, the remaining issue can cause panics or excessive resource use, and scanners will continue to flag this dependency despite the PR’s vulnerability-remediation goal.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed v5.19.1 release

This security update pins github.com/go-git/go-git/v5 to v5.19.0, but the current GHSA-w5pp-99ch-qj29 advisory marks all versions before 5.19.1 as affected by denial-of-service issues when go-git clones, fetches, opens, or otherwise processes malicious Git repository data. In e2e code paths that interact with an untrusted or compromised remote repository, this leaves the module vulnerable and will continue to trip dependency scanning; use v5.19.1 or newer instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade go-git to a non-vulnerable patch

This remediation pins github.com/go-git/go-git/v5 to v5.19.0, but the current advisories for CVE-2026-45570 and CVE-2026-45571 state that versions before v5.19.1 remain vulnerable and are fixed in v5.19.1. In e2e-framework runs where Pulumi/go-git handles SSH repository URLs with quoted paths or crafted repositories/submodules, the SSH escaping and path-validation issues remain, and dependency scanners will still flag this module; please bump to v5.19.1 or later instead of stopping at v5.19.0.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the fixed patch release

This security bump pins github.com/go-git/go-git/v5 to v5.19.0, but that version is still in the affected range for current go-git advisories such as GHSA-w5pp-99ch-qj29 and CVE-2026-45570/CVE-2026-45571, which list v5.19.1 as the fixed release. In environments that run vulnerability checks against test/e2e-framework, this update will continue to report go-git as vulnerable; bump the dependency to v5.19.1 instead.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump go-git to the patched 5.19.1 release

For this vulnerability-remediation update, pinning github.com/go-git/go-git/v5 to v5.19.0 still leaves the module on a version affected by current go-git advisories: the upstream GHSA-m7cr-m3pv-hgrp advisory marks <=5.19.0 as affected and 5.19.1 as patched. In any e2e-framework path that clones or fetches attacker-controlled SSH repository URLs, this keeps the same class of exposure and security scanners can continue flagging the module, so the dependency should be bumped to at least v5.19.1.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade go-git past vulnerable v5.19.0

This security-remediation bump selects github.com/go-git/go-git/v5 v5.19.0, but GitHub advisory GHSA-w5pp-99ch-qj29 lists <=5.19.0 as affected and 5.19.1 as the patched version (GHSA-w5pp-99ch-qj29). As a result, dependency scanning can still flag this module, and any e2e-framework path that processes untrusted Git repository data via this transitive dependency remains exposed to the documented DoS issue.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Upgrade go-git to the patched 5.19.1 release

This remediation pins github.com/go-git/go-git/v5 to v5.19.0, but current advisories still classify all versions before 5.19.1 as affected by malicious-repository issues, including path validation allowing crafted repos to modify .git directories and malformed object data causing panics/resource exhaustion (see https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/CVE-2026-45571/ and https://advisories.gitlab.com/golang/github.com/go-git/go-git/v5/GHSA-w5pp-99ch-qj29/). In environments where the e2e framework’s transitive go-git dependency processes untrusted repos, this leaves the module vulnerable and dependency scanning will keep flagging it; please bump to v5.19.1 or newer instead.

Useful? React with 👍 / 👎.

github.com/go-logr/logr v1.4.3 // indirect
github.com/go-logr/stdr v1.2.2 // indirect
github.com/go-openapi/jsonpointer v0.23.1 // indirect
Expand Down Expand Up @@ -179,6 +179,7 @@ require (
github.com/json-iterator/go v1.1.12 // indirect
github.com/kevinburke/ssh_config v1.2.0 // indirect
github.com/klauspost/compress v1.18.6 // indirect
github.com/klauspost/cpuid/v2 v2.3.0 // indirect
github.com/kr/fs v0.1.0 // indirect
github.com/liggitt/tabwriter v0.0.0-20181228230101-89fcab3d43de // indirect
github.com/lucasb-eyer/go-colorful v1.4.0 // indirect
Expand Down Expand Up @@ -209,7 +210,7 @@ require (
github.com/peterbourgon/diskv v2.0.1+incompatible // indirect
github.com/pgavlin/fx v0.1.6 // indirect
github.com/philhofer/fwd v1.2.0 // indirect
github.com/pjbgf/sha1cd v0.3.2 // indirect
github.com/pjbgf/sha1cd v0.6.0 // indirect
github.com/pkg/errors v0.9.1 // indirect
github.com/pkg/term v1.1.0 // indirect
github.com/planetscale/vtprotobuf v0.6.1-0.20240319094008-0393e58bdf10 // indirect
Expand Down
14 changes: 8 additions & 6 deletions test/e2e-framework/go.sum

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading