Skip to content

OCPBUGS-67374,OCPBUGS-67472: CVE-2025-65637 - bump github.com/sirupsen/logrus to v1.9.3 [4.12]#2596

Open
rissh wants to merge 1 commit intoopenshift:release-4.12from
rissh:fix/CVE-2025-65637-4.12
Open

OCPBUGS-67374,OCPBUGS-67472: CVE-2025-65637 - bump github.com/sirupsen/logrus to v1.9.3 [4.12]#2596
rissh wants to merge 1 commit intoopenshift:release-4.12from
rissh:fix/CVE-2025-65637-4.12

Conversation

@rissh
Copy link

@rissh rissh commented Feb 19, 2026

Backport of #2573 to release-4.12.

Bumps github.com/sirupsen/logrus from v1.9.0 to v1.9.3 to address GHSA-4f99-4q7p-p3gh.

Related PRs:

release-4.17: #2573
release-4.16: #2582
release-4.15: #2583
release-4.14: #2586

@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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 19, 2026
@openshift-ci-robot
Copy link

@rissh: This pull request references Jira Issue OCPBUGS-67374, which is invalid:

  • expected dependent Jira Issue OCPBUGS-67556 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

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.

This pull request references Jira Issue OCPBUGS-67472, which is invalid:

  • expected dependent Jira Issue OCPBUGS-67652 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

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:

Backport of xx to release-4.12.

Bumps github.com/sirupsen/logrus from v1.9.0 to v1.9.3 to address GHSA-4f99-4q7p-p3gh.

Related PRs:

release-4.17: #2573
release-4.16: #2582
release-4.15: #2583
release-4.14: #2586

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-ci-robot
Copy link

@rissh: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested a review from deads2k February 19, 2026 11:26
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Feb 19, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rissh
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

@openshift-ci-robot
Copy link

@rissh: This pull request references Jira Issue OCPBUGS-67374, which is invalid:

  • expected dependent Jira Issue OCPBUGS-67556 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

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.

This pull request references Jira Issue OCPBUGS-67472, which is invalid:

  • expected dependent Jira Issue OCPBUGS-67652 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

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:

Backport of #2573 to release-4.12.

Bumps github.com/sirupsen/logrus from v1.9.0 to v1.9.3 to address GHSA-4f99-4q7p-p3gh.

Related PRs:

release-4.17: #2573
release-4.16: #2582
release-4.15: #2583
release-4.14: #2586

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.

@rissh
Copy link
Author

rissh commented Feb 19, 2026

/retest

@openshift-ci
Copy link

openshift-ci bot commented Feb 19, 2026

@rissh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/unit f579dcd link true /test unit
ci/prow/e2e-gcp f579dcd link true /test e2e-gcp
ci/prow/e2e-gcp-ovn-upgrade f579dcd link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-fips f579dcd link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-serial f579dcd link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-cgroupsv2 f579dcd link true /test e2e-aws-ovn-cgroupsv2
ci/prow/images f579dcd link true /test images
ci/prow/k8s-e2e-gcp-ovn f579dcd link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-aws-ovn-crun f579dcd link true /test e2e-aws-ovn-crun
ci/prow/k8s-e2e-gcp-serial f579dcd link true /test k8s-e2e-gcp-serial
ci/prow/k8s-e2e-conformance-aws f579dcd link true /test k8s-e2e-conformance-aws

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.

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

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants