Skip to content

OCPBUGS-67322: Fix CVE-2025-66564 by updating build tooling#149

Open
aman4433 wants to merge 1 commit intoopenshift:release-4.18from
aman4433:fix/CVE-2025-66564-release-4.18
Open

OCPBUGS-67322: Fix CVE-2025-66564 by updating build tooling#149
aman4433 wants to merge 1 commit intoopenshift:release-4.18from
aman4433:fix/CVE-2025-66564-release-4.18

Conversation

@aman4433
Copy link
Contributor

@aman4433 aman4433 commented Jan 21, 2026

This PR fixes CVE-2025-66564 by updating build-time tooling under hack/tools,
including upgrading cosign to v2, which removes the vulnerable
timestamp-authority v1 dependency.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 Jan 21, 2026
@openshift-ci-robot
Copy link

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

This PR fixes GHSA-4qg8-fj49-pxjh by updating build-time tooling under hack/tools,
including upgrading cosign to v2, which removes the vulnerable
timestamp-authority v1 dependency.

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 openshift-ci bot requested review from nrb and theobarberbany January 21, 2026 14:58
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 21, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign radekmanak 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 Jan 21, 2026

@aman4433: 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/unit 5bb0d2f link true /test unit
ci/prow/generate 5bb0d2f link true /test generate

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-important Referenced Jira bug's severity is important 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