OCPBUGS-68220: Update logrus to 1.9.3 to address CVE-2025-65637

[davegord]

Summary

• Updates github.com/sirupsen/logrus from v1.9.0 to v1.9.3
• Fixes CVE-2025-65637 security vulnerability in the logrus logging library

Changes

• Updated go.mod with logrus v1.9.3
• Ran go mod tidy and go mod vendor to update dependencies
• Vendored updated logrus package with security fix

Test plan

• Verify go.mod and go.sum changes are correct
• Run unit tests
• Build the operator
• Deploy and verify functionality

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk dependency update focused on a vendored logging library; main impact is in logrus WriterLevel scanning behavior, which could slightly change log line splitting/formatting for very large writes.

Overview
Updates vendored github.com/sirupsen/logrus from v1.9.0 to v1.9.3 (including go.mod/go.sum/vendor/modules.txt) to pick up the CVE fix.

The updated logrus writer.go changes how Entry.WriterLevel reads from the pipe: it configures the scanner to safely handle large inputs (chunking up to bufio.MaxScanTokenSize) and trims trailing \r\n before logging, plus minor README/vendor doc adjustments.

^{Written by Cursor Bugbot for commit c573cef. This will update automatically on new commits. Configure here.}

^{Cursor Bugbot reviewed your changes and found no issues for commit c573cef}

[coderabbitai]

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.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[openshift-ci-robot]

@davegord: This pull request references Jira Issue OCPBUGS-68220, 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-68220 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:

Summary

• Updates github.com/sirupsen/logrus from v1.9.0 to v1.9.3
• Fixes CVE-2025-65637 security vulnerability in the logrus logging library

Changes

• Updated go.mod with logrus v1.9.3
• Ran go mod tidy and go mod vendor to update dependencies
• Vendored updated logrus package with security fix

Test plan

• Verify go.mod and go.sum changes are correct
• Run unit tests
• Build the operator
• Deploy and verify functionality

🤖 Generated with Claude Code

---

[!NOTE]
Low Risk
Low risk dependency update focused on a vendored logging library; main impact is in logrus WriterLevel scanning behavior, which could slightly change log line splitting/formatting for very large writes.

Overview
Updates vendored github.com/sirupsen/logrus from v1.9.0 to v1.9.3 (including go.mod/go.sum/vendor/modules.txt) to pick up the CVE fix.

The updated logrus writer.go changes how Entry.WriterLevel reads from the pipe: it configures the scanner to safely handle large inputs (chunking up to bufio.MaxScanTokenSize) and trims trailing \r\n before logging, plus minor README/vendor doc adjustments.

^{Written by Cursor Bugbot for commit c573cef. This will update automatically on new commits. Configure here.}

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.

[davegord]

/jira refresh

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• OWNERS

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]

@davegord: This pull request references Jira Issue OCPBUGS-68220, 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 New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-75924 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-75924 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

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-ci-robot]

@davegord: This pull request references Jira Issue OCPBUGS-68220, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-75924 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-75924 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

Details

In response to this:

Summary

• Updates github.com/sirupsen/logrus from v1.9.0 to v1.9.3
• Fixes CVE-2025-65637 security vulnerability in the logrus logging library

Changes

• Updated go.mod with logrus v1.9.3
• Ran go mod tidy and go mod vendor to update dependencies
• Vendored updated logrus package with security fix

Test plan

• Verify go.mod and go.sum changes are correct
• Run unit tests
• Build the operator
• Deploy and verify functionality

🤖 Generated with Claude Code

---

[!NOTE]
Low Risk
Low risk dependency update focused on a vendored logging library; main impact is in logrus WriterLevel scanning behavior, which could slightly change log line splitting/formatting for very large writes.

Overview
Updates vendored github.com/sirupsen/logrus from v1.9.0 to v1.9.3 (including go.mod/go.sum/vendor/modules.txt) to pick up the CVE fix.

The updated logrus writer.go changes how Entry.WriterLevel reads from the pipe: it configures the scanner to safely handle large inputs (chunking up to bufio.MaxScanTokenSize) and trims trailing \r\n before logging, plus minor README/vendor doc adjustments.

^{Written by Cursor Bugbot for commit c573cef. This will update automatically on new commits. Configure here.}

^{Cursor Bugbot reviewed your changes and found no issues for commit c573cef}

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]

@davegord: 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/unit	c573cef	link	true	/test unit

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.