Skip to content

Comments

OCPBUGS-67987:CVE-2025-65637 openshift4/ose-kube-proxy-rhel9: github.com/sirupsen/logrus: Denial-of-Service due to large single-line payload [openshift-4.15.z]#910

Open
katekeiroz-dev wants to merge 1 commit intoopenshift:release-4.15from
katekeiroz-dev:CVE-2025-65637-4.15
Open

OCPBUGS-67987:CVE-2025-65637 openshift4/ose-kube-proxy-rhel9: github.com/sirupsen/logrus: Denial-of-Service due to large single-line payload [openshift-4.15.z]#910
katekeiroz-dev wants to merge 1 commit intoopenshift:release-4.15from
katekeiroz-dev:CVE-2025-65637-4.15

Conversation

@katekeiroz-dev
Copy link

Bumps the logrus module in go.mod from github.com/sirupsen/logrus@v1.9.0 to github.com/sirupsen/logrus@v1.9.3

…com/sirupsen/logrus: Denial-of-Service due to large single-line payload [openshift-4.15.z]
@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 12, 2026
@openshift-ci-robot
Copy link

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-67987, 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-67987 to depend on a bug targeting a version in 4.16.0, 4.16.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:

Bumps the logrus module in go.mod from github.com/sirupsen/logrus@v1.9.0 to github.com/sirupsen/logrus@v1.9.3

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
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: katekeiroz-dev
Once this PR has been reviewed and has the lgtm label, please assign ingvagabund 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
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

@katekeiroz-dev: The following test 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/security 59eb688 link false /test security

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

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants