Fix vulnerabilities reported by trivy #2088
Closed
Conversation
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
- Update Go version from 1.24.4 to 1.24.6 to fix CVE-2025-47907 and CVE-2025-4674
sanikachavan5
changed the title
sanikachavan5
force-pushed
the
sanikachavan5/fix-vulnerabilities-reported-by-trivy
branch
from
5b92e07 to
dff928e
Compare
sanikachavan5
deleted the
sanikachavan5/fix-vulnerabilities-reported-by-trivy
branch
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.
PCI review checklist
This pull request updates the Go version used in the project from 1.24.4 to 1.24.6. This ensures that the codebase uses the latest patch release, which typically includes important bug fixes and security updates.
Go version upgrade:
.go-version: Updated the Go version from 1.24.4 to 1.24.6.go.mod: Updated the Go version declaration from 1.24.4 to 1.24.6.[Copilot is generating a summary...]
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.