Skip to content

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

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.12from
rissh:fix/CVE-2025-65637-4.12
Apr 11, 2026
Merged

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

Conversation

@rissh
Copy link
Copy Markdown

@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
Copy Markdown

@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
Copy Markdown

@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-robot
Copy link
Copy Markdown

@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
Copy Markdown
Author

rissh commented Feb 19, 2026

/retest

3 similar comments
@rissh
Copy link
Copy Markdown
Author

rissh commented Mar 6, 2026

/retest

@rissh
Copy link
Copy Markdown
Author

rissh commented Mar 16, 2026

/retest

@rissh
Copy link
Copy Markdown
Author

rissh commented Mar 25, 2026

/retest

@rissh
Copy link
Copy Markdown
Author

rissh commented Mar 28, 2026

/jira refresh
/retest

@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 Mar 28, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rissh: This pull request references Jira Issue OCPBUGS-67374, 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.12.z) matches configured target version for branch (4.12.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-67556 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-67556 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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.

This pull request references Jira Issue OCPBUGS-67472, 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.12.z) matches configured target version for branch (4.12.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-67652 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-67652 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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
/retest

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
Copy Markdown

coderabbitai Bot commented Mar 28, 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.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b82215fa-9c73-434e-b269-014500b9cc46

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

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.

@rissh
Copy link
Copy Markdown
Author

rissh commented Mar 31, 2026

/retest

@dusk125
Copy link
Copy Markdown

dusk125 commented Apr 10, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 10, 2026
@sjenning sjenning added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Apr 10, 2026
@sjenning
Copy link
Copy Markdown

/approve
/override ci/prow/e2e-aws-ovn-serial

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 10, 2026

@sjenning: Overrode contexts on behalf of sjenning: ci/prow/e2e-aws-ovn-serial

Details

In response to this:

/approve
/override ci/prow/e2e-aws-ovn-serial

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.

@rissh
Copy link
Copy Markdown
Author

rissh commented Apr 10, 2026

/verified later @rissh

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Apr 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rissh: This PR has been marked to be verified later by @rissh.

Details

In response to this:

/verified later @rissh

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
Copy Markdown
Author

rissh commented Apr 10, 2026

Hey @deads2k,
Can you please approve this PR?

@sjenning sjenning added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 10, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: dusk125, rissh, sjenning

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-merge-bot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 0b39b41 and 2 for PR HEAD f579dcd in total

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 11, 2026

@rissh: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 2fcda8a into openshift:release-4.12 Apr 11, 2026
16 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@rissh: An error was encountered invalid pull identifier with 2 parts: "mjuanxd/logrus-dos-poc" for bug OCPBUGS-67374 on the Jira server at https://redhat.atlassian.net. 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 OCPBUGS-67374: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-67374 has been moved to the MODIFIED state.

An error was encountered invalid pull identifier with 2 parts: "mjuanxd/logrus-dos-poc" for bug OCPBUGS-67472 on the Jira server at https://redhat.atlassian.net. 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 OCPBUGS-67472: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-67472 has been moved to the MODIFIED state.

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
Copy Markdown
Author

rissh commented Apr 11, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@rissh: Jira Issue OCPBUGS-67374 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

Jira Issue OCPBUGS-67472 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

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.

@openshift-merge-robot
Copy link
Copy Markdown

Fix included in release 4.12.0-0.nightly-2026-04-13-115747

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. vendor-update Touching vendor dir or related files verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants