chore(deps): bump golang.org/x/oauth2 from 0.25.0 to 0.27.0 - resolve CVE-2025-22868 #2480
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.
Description
Let's keep the AquaSec Trivy-Operator dependency
golang.org/x/oauth2
up-to-date. The current latest Docker-Image tag0.25.0
using an older version of oauth2 which could be affected by golang/go#71490 (https://nvd.nist.gov/vuln/detail/CVE-2025-22868). So, let's upgrade oauth2 from0.25.0
to0.27.0
for AquaSec Trivy-Operator.Having this said, I ran:
Note for Reviewers
Basically, this dependency update just aim to silence some (SBOM-based) scanners, while checking
aquasec/trivy-operator:0.25.0
Docker-Image.I didn't create a linked issue here in the repo yet - If this would be better/required to have an issue, I'm happy to create one and link this here with Close/Fixed reference.