Skip to content

OCPBUGS-68150: Update library-go to fix CVE-2025-65637#840

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.17from
amitesh1201:fix-cve-2025-65637-logrus
Feb 18, 2026
Merged

OCPBUGS-68150: Update library-go to fix CVE-2025-65637#840
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.17from
amitesh1201:fix-cve-2025-65637-logrus

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
@amitesh1201
Copy link
Author

/assign @deads2k

@amitesh1201
Copy link
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 16, 2026
@openshift-ci-robot
Copy link
Contributor

@amitesh1201: This pull request references Jira Issue OCPBUGS-68150, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-76946 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-76946 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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.

@benluddy benluddy added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 18, 2026
@benluddy
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 18, 2026
@benluddy
Copy link
Contributor

/verified by @amitesh1201

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: amitesh1201, liouk

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

The pull request process is described 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

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 18, 2026
@openshift-ci-robot
Copy link
Contributor

@benluddy: This PR has been marked as verified by @amitesh1201.

Details

In response to this:

/verified by @amitesh1201

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 9f93caf into openshift:release-4.17 Feb 18, 2026
11 checks passed
@openshift-ci-robot
Copy link
Contributor

@amitesh1201: An error was encountered invalid pull identifier with 2 parts: "mjuanxd/logrus-dos-poc" for bug OCPBUGS-68150 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message.

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.Jira Issue Verification Checks: Jira Issue OCPBUGS-68150
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-68150 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

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.

@amitesh1201 amitesh1201 deleted the fix-cve-2025-65637-logrus branch February 19, 2026 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants