Skip to content

[release-4.17] OCPBUGS-81861: Bump go-jose/go-jose/v4@v4.1.4#1039

Open
katekeiroz-dev wants to merge 1 commit into
openshift:release-4.17from
katekeiroz-dev:CVE-2026-34986-4.17
Open

[release-4.17] OCPBUGS-81861: Bump go-jose/go-jose/v4@v4.1.4#1039
katekeiroz-dev wants to merge 1 commit into
openshift:release-4.17from
katekeiroz-dev:CVE-2026-34986-4.17

Conversation

@katekeiroz-dev

Copy link
Copy Markdown

CVE-2026-34986

Replace github.com/go-jose/go-jose/v4 with the OpenShift sustaining fork to backport the CVE-2026-34986 fix onto v4.0.5 without bumping to v4.1.4 or requiring Go 1.24.

Compliance dependency bump; CCO does not use vulnerable JWE code paths.

Related: OCPBUGS-81861

…VE-2026-34986

Replace github.com/go-jose/go-jose/v4 with the OpenShift sustaining fork
to backport the CVE-2026-34986 fix onto v4.0.5 without bumping to v4.1.4
or requiring Go 1.24.

Compliance dependency bump; CCO does not use vulnerable JWE code paths.

Related: OCPBUGS-81861
@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. labels Jun 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81861, which is invalid:

  • expected dependent Jira Issue OCPBUGS-81887 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:

…CVE-2026-34986

Replace github.com/go-jose/go-jose/v4 with the OpenShift sustaining fork to backport the CVE-2026-34986 fix onto v4.0.5 without bumping to v4.1.4 or requiring Go 1.24.

Compliance dependency bump; CCO does not use vulnerable JWE code paths.

Related: OCPBUGS-81861

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 18, 2026
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ae435389-c3b5-46f1-9689-90299d2ef0d0

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.

@openshift-ci openshift-ci Bot requested review from 2uasimojo and jstuever June 18, 2026 15:12
@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: katekeiroz-dev
Once this PR has been reviewed and has the lgtm label, please assign dlom 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

@katekeiroz-dev

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81861, which is invalid:

  • expected dependent Jira Issue OCPBUGS-81887 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:

/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.

@katekeiroz-dev

Copy link
Copy Markdown
Author

/ok-to-test

@openshift-ci openshift-ci Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jun 18, 2026
@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@katekeiroz-dev: 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/e2e-hypershift 5622b03 link true /test e2e-hypershift

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.

@codecov

codecov Bot commented Jun 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.82%. Comparing base (662db76) to head (5622b03).

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff              @@
##           release-4.17    #1039   +/-   ##
=============================================
  Coverage         46.82%   46.82%           
=============================================
  Files                97       97           
  Lines             11896    11896           
=============================================
  Hits               5570     5570           
  Misses             5709     5709           
  Partials            617      617           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants