[release-4.13] OCPBUGS-54618: bump ovnver to prevent CVE-2025-0650 being flagged

[jluhrsen]

Dockerfile.base had 23.06.1-112.el9fdp but according to this
Security Advisory [0], it was resolved in 23.06.4-26

also, Dockerfile.fedora in dist/images/ was using and
23.06.0-0.fc37 so bumping to 23.06.4-26 per the same
Security Advisory

[0] https://access.redhat.com/errata/RHSA-2025:1094

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

• My code requires changes to the documentation
• if so, I have updated the documentation as required
• My code requires tests
• if so, I have added and/or updated the tests as required
• All the tests have passed in the CI

How to verify it

[openshift-ci-robot]

@jluhrsen: This pull request references Jira Issue OCPBUGS-54618, which is invalid:

• expected the bug to target either version "4.13." or "openshift-4.13.", but it targets "4.15.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-54618 to depend on a bug targeting a version in 4.14.0, 4.14.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.

In response to this:

Security Advisory [0], it was resolved in 23.06-23.06.4-26

also, Dockerfile.fedora in dist/images/ was using and 23.06.0-0.fc37 so bumping to 23.06-23.06.4-26 per the same Security Advisory

[0] https://access.redhat.com/errata/RHSA-2025:1094

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

• My code requires changes to the documentation
• if so, I have updated the documentation as required
• My code requires tests
• if so, I have added and/or updated the tests as required
• All the tests have passed in the CI

How to verify it

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jluhrsen
Once this PR has been reviewed and has the lgtm label, please assign jcaamano for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

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

[jluhrsen]

/retest

[jluhrsen]

/retest

[jluhrsen]

/retest

[jluhrsen]

/test e2e-aws-ovn-hypershift

[openshift-ci]

@jluhrsen: 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/e2e-aws-ovn-hypershift	a992b03	link	false	/test e2e-aws-ovn-hypershift
ci/prow/e2e-vsphere-ovn	a992b03	link	false	/test e2e-vsphere-ovn
ci/prow/security	a992b03	link	false	/test security

Full PR test history. Your PR dashboard.

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

PR needs rebase.

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.