OCPBUGS-68209: fix CVE-2025-65637 #357

eshulman2 · 2025-12-16T08:40:29Z

What this PR does / why we need it:
Update logrus version to v1.9.1 to avoid issue described in CVE-2025-65637

Special notes for reviewers:
CVE fix

Release note:

NONE

Update logrus version to v1.9.1 to avoid issue described in CVE-2025-65637

openshift-ci-robot · 2025-12-16T08:40:37Z

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

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.

eshulman2 · 2025-12-16T08:44:47Z

/jira refresh

openshift-ci-robot · 2025-12-16T08:44:52Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68210, which is invalid:

expected Jira Issue OCPBUGS-68210 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:

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 · 2025-12-16T11:18:36Z

@eshulman2: 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	`1ae23c3`	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.

openshift-ci-robot · 2025-12-21T12:58:28Z

@eshulman2: This pull request references Jira Issue OCPBUGS-70088, which is invalid:

expected the bug to target either version "4.17." or "openshift-4.17.", but it targets "4.18.z" instead
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-70088 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:

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.

eshulman2 · 2025-12-21T12:58:35Z

/jira refresh

openshift-ci-robot · 2025-12-21T12:58:39Z

@eshulman2: This pull request references Jira Issue OCPBUGS-70088, which is invalid:

expected the bug to target either version "4.17." or "openshift-4.17.", but it targets "4.18.z" instead
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-70088 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:

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.

eshulman2 · 2025-12-21T13:02:11Z

/jira refresh

openshift-ci-robot · 2025-12-21T13:02:15Z

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

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.

eshulman2 · 2025-12-21T13:10:06Z

/jira refresh

openshift-ci-robot · 2025-12-21T13:10:11Z

@eshulman2: This pull request references Jira Issue OCPBUGS-70088, 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 dependent Jira Issue OCPBUGS-70103 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Not a Bug) instead
expected dependent Jira Issue OCPBUGS-70103 to target a version in 4.18.0, 4.18.z, but it targets "4.18" 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:

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.

eshulman2 · 2025-12-21T13:11:06Z

/jira refresh

openshift-ci-robot · 2025-12-21T13:11:11Z

@eshulman2: This pull request references Jira Issue OCPBUGS-70088, 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.

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:

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 · 2025-12-21T13:14:05Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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 dependent Jira Issue OCPBUGS-69416 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Duplicate) 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:

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.

eshulman2 · 2025-12-21T13:14:14Z

/jira refresh

openshift-ci-robot · 2025-12-21T13:14:19Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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 dependent Jira Issue OCPBUGS-69416 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Duplicate) 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:

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.

eshulman2 · 2025-12-22T09:19:01Z

/jira refresh

openshift-ci-robot · 2025-12-22T09:19:05Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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 dependent Jira Issue OCPBUGS-69416 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Duplicate) instead
expected dependent Jira Issue OCPBUGS-68105 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
expected dependent Jira Issue OCPBUGS-68105 to target a version in 4.18.0, 4.18.z, but it targets "4.16.z" instead
dependent bug OSASINFRA-3999 is not in the required OCPBUGS project

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:

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.

eshulman2 · 2025-12-22T10:30:40Z

/jira refresh

openshift-ci-robot · 2025-12-22T10:30:45Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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 dependent Jira Issue OCPBUGS-70103 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
dependent bug OSASINFRA-3999 is not in the required OCPBUGS project

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:

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 · 2025-12-22T10:58:16Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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 dependent Jira Issue OCPBUGS-70103 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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:

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.

eshulman2 · 2025-12-22T13:10:09Z

/jira refresh

openshift-ci-robot · 2025-12-22T13:10:14Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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 dependent Jira Issue OCPBUGS-70103 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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:

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.

eshulman2 · 2025-12-22T13:14:47Z

/jira refresh

openshift-ci-robot · 2025-12-22T13:14:51Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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.

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:

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.

eshulman2 · 2025-12-22T13:37:04Z

@stephenfin @mdbooth the security issues detected by synk indeed exist but are outside the scope of this patch, what should I do?

eshulman2 · 2025-12-22T14:30:22Z

/jira refresh

openshift-ci-robot · 2025-12-22T14:30:31Z

@eshulman2: This pull request references Jira Issue OCPBUGS-68209, 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-70103 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-70103 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:

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.

gryf

/lgtm
/approve

openshift-ci · 2026-01-05T11:03:29Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eshulman2, gryf

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:

~~DOWNSTREAM_OWNERS~~ [gryf]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

eshulman2 · 2026-01-05T11:15:51Z

/verify by ci

gryf · 2026-01-05T11:18:09Z

/label backport-risk-assessed

openshift-ci · 2026-01-05T11:18:38Z

@gryf: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers]

Details

In response to this:

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.

mandre

/label backport-risk-assessed

mandre · 2026-01-05T13:24:06Z

/verified later @eshulman2

openshift-ci-robot · 2026-01-05T13:24:19Z

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

Details

In response to this:

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 · 2026-01-05T13:28:18Z

@eshulman2: An error was encountered invalid pull identifier with 2 parts: "mjuanxd/logrus-dos-poc" for bug OCPBUGS-68209 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 OCPBUGS-68209: 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-68209 has been moved to the MODIFIED state.

Details

In response to this:

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 · 2026-01-05T21:56:39Z

Fix included in accepted release 4.17.0-0.nightly-2026-01-05-181130

OCPBUGS-68210: fix CVE-2025-65637

1ae23c3

Update logrus version to v1.9.1 to avoid issue described in CVE-2025-65637

openshift-ci bot requested review from mdbooth and stephenfin December 16, 2025 08:40

eshulman2 changed the title ~~OCPBUGS-68210: fix CVE-2025-65637~~ OCPBUGS-70088: fix CVE-2025-65637 Dec 21, 2025

openshift-ci-robot removed the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Dec 21, 2025

eshulman2 changed the title ~~OCPBUGS-70088: fix CVE-2025-65637~~ OCPBUGS-68209: fix CVE-2025-65637 Dec 21, 2025

openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Dec 21, 2025

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 Dec 22, 2025

gryf reviewed Jan 5, 2026

View reviewed changes

openshift-ci bot assigned gryf Jan 5, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2026

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2026

mandre reviewed Jan 5, 2026

View reviewed changes

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 5, 2026

openshift-ci bot assigned eurijon, imatza-rh and itzikb-redhat Jan 5, 2026

openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Jan 5, 2026

openshift-merge-bot bot merged commit baec201 into openshift:release-4.17 Jan 5, 2026
5 of 6 checks passed

OCPBUGS-68209: fix CVE-2025-65637 #357

OCPBUGS-68209: fix CVE-2025-65637 #357

Uh oh!

Conversation

eshulman2 commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Uh oh!

eshulman2 commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Uh oh!

openshift-ci bot commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

eshulman2 commented Dec 21, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

eshulman2 commented Dec 21, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

eshulman2 commented Dec 21, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

eshulman2 commented Dec 21, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

eshulman2 commented Dec 21, 2025

Uh oh!

openshift-ci-robot commented Dec 21, 2025

Uh oh!

eshulman2 commented Dec 22, 2025

Uh oh!

openshift-ci-robot commented Dec 22, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

eshulman2 commented Dec 22, 2025

Uh oh!

openshift-ci-robot commented Dec 22, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 22, 2025

Uh oh!

eshulman2 commented Dec 22, 2025

Uh oh!

openshift-ci-robot commented Dec 22, 2025

Uh oh!

eshulman2 commented Dec 22, 2025

Uh oh!

openshift-ci-robot commented Dec 22, 2025

Uh oh!

eshulman2 commented Dec 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

eshulman2 commented Dec 22, 2025

Uh oh!

openshift-ci-robot commented Dec 22, 2025

Uh oh!

gryf left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Jan 5, 2026

Uh oh!

eshulman2 commented Jan 5, 2026

Uh oh!

gryf commented Jan 5, 2026

Uh oh!

openshift-ci bot commented Jan 5, 2026

Uh oh!

mandre left a comment

Choose a reason for hiding this comment

Uh oh!

mandre commented Jan 5, 2026

openshift-ci-robot commented Dec 22, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 22, 2025 •

edited by openshift-ci bot

Loading

eshulman2 commented Dec 22, 2025 •

edited

Loading