Skip to content

Conversation

@amitesh1201
Copy link

Description

OCPBUGS-68150: deps: Update github.com/openshift/library-go from v0.0.0-20241023075405-e3586cc1ab21 to v0.0.0-20260202164332-cedbe1daf8d0 to fix CVE-2025-65637 (DoS vulnerability in logrus).

Changes

  • Updated github.com/openshift/library-go to commit cedbe1daf8d0876c55731ad53934bbb243541d94
  • Indirectly updates github.com/sirupsen/logrus from v1.9.0 to v1.9.3

CVE Information

  • CVE ID: CVE-2025-65637
  • Severity: High (CVSS 7.5)
  • Vulnerable Versions: < 1.8.3, >= 1.9.0 < 1.9.1, >= 1.9.2 < 1.9.3
  • Fixed Version: v1.9.3
  • Impact: Denial of Service (DoS) vulnerability

Testing

  • go build ./... successful
  • Verified logrus version: go list -m github.com/sirupsen/logrus shows v1.9.3
  • Verified library-go version includes fix commit

Update github.com/openshift/library-go to include commit cedbe1daf8d0876c55731ad53934bbb243541d94
which updates logrus from v1.9.0 to v1.9.3, fixing CVE-2025-65637
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 10, 2026
@openshift-ci-robot
Copy link
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-68150, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-68150 to depend on a bug targeting a version in 4.18.0, 4.18.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Description

OCPBUGS-68150: deps: Update github.com/openshift/library-go from v0.0.0-20241023075405-e3586cc1ab21 to v0.0.0-20260202164332-cedbe1daf8d0 to fix CVE-2025-65637 (DoS vulnerability in logrus).

Changes

  • Updated github.com/openshift/library-go to commit cedbe1daf8d0876c55731ad53934bbb243541d94
  • Indirectly updates github.com/sirupsen/logrus from v1.9.0 to v1.9.3

CVE Information

  • CVE ID: CVE-2025-65637
  • Severity: High (CVSS 7.5)
  • Vulnerable Versions: < 1.8.3, >= 1.9.0 < 1.9.1, >= 1.9.2 < 1.9.3
  • Fixed Version: v1.9.3
  • Impact: Denial of Service (DoS) vulnerability

Testing

  • go build ./... successful
  • Verified logrus version: go list -m github.com/sirupsen/logrus shows v1.9.3
  • Verified library-go version includes fix commit

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai
Copy link

coderabbitai bot commented Feb 10, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from ibihim and liouk February 10, 2026 07:46
@amitesh1201
Copy link
Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2026

@amitesh1201: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@amitesh1201
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-68150, which is invalid:

  • expected Jira Issue OCPBUGS-68150 to depend on a bug targeting a version in 4.18.0, 4.18.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@liouk
Copy link
Member

liouk commented Feb 12, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 12, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amitesh1201, liouk
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants