fix: upgrade runc to v1.2.8 for security CVEs#10
Merged
Conversation
- Upgraded github.com/opencontainers/runc from v1.2.3 to v1.2.8 to fix: - CVE-2025-31133 (High severity) - CVE-2025-52565 (High severity) - CVE-2025-52881 (High severity) - CVE-2026-41579 (Moderate severity) - github.com/jackc/pgx/v4 v4.18.3 is already the latest release in the v4 major version line. pgx/v5 is the current major version (up to v5.10.0), but upgrading to v5 would be a breaking API change. No further v4 patches are available. - github.com/jackc/pgproto3/v2 v2.3.3 is already the latest release in the v2 line. It is tied to pgx/v4 and has no further patches available. Co-authored-by: Aaron Longwell <27492+adlio@users.noreply.github.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 7 7
Lines 216 216
=========================================
Hits 216 216 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
2 participants
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 pull request was created by @kiro-agent on behalf of @adlio 👻
Comment with /kiro fix to address specific feedback or /kiro all to address everything.
Learn about Kiro Web
Summary
Addresses GitHub security alerts for vulnerable dependencies in
go.mod.Changes
github.com/opencontainers/runcfrom v1.2.3 to v1.2.8Dependencies with no available patches
github.com/jackc/pgx/v4v4.18.3 - This is the latest and final release in the v4 major version line. The maintainer has moved to pgx/v5 (currently at v5.10.0). Resolving this alert requires migrating the library to the pgx/v5 API, which is a breaking change and out of scope for this security patch.github.com/jackc/pgproto3/v2v2.3.3 - This is the latest and final release in the v2 line. It is a transitive dependency of pgx/v4 and cannot be updated independently. It will be resolved when/if the library migrates to pgx/v5.Testing
go build ./...passes cleanlygo mod tidyproduces no additional changes