[release-4.16] OCPBUGS-81849: Bump go-jose/go-jose/v4@v4.1.4

[katekeiroz-dev]

…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-81849

[openshift-ci-robot]

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

• expected the vulnerability to target either version "4.16." or "openshift-4.16.", but it targets "4.17.z" instead
• 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
• expected dependent Jira Issue OCPBUGS-81887 to target a version in 4.17.0, 4.17.z, but it targets "4.18.z" 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-81849

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.

[coderabbitai]

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: a6360eee-1344-497d-9698-f5fea5028a1a

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[katekeiroz-dev]

/ok-to-test

[openshift-ci]

[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 suhanime 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

[katekeiroz-dev]

/jira-refresh

[katekeiroz-dev]

/jira refresh

[openshift-ci-robot]

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

• expected the vulnerability to target either version "4.16." or "openshift-4.16.", but it targets "4.17.z" instead
• 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
• expected dependent Jira Issue OCPBUGS-81887 to target a version in 4.17.0, 4.17.z, but it targets "4.18.z" 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.

[openshift-ci-robot]

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81849, 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-81861 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-81849

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]

/jira refresh

[openshift-ci-robot]

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81849, 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-81861 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.25%. Comparing base (d66c192) to head (89bf30c).

Additional details and impacted files

@@              Coverage Diff              @@
##           release-4.16    #1040   +/-   ##
=============================================
  Coverage         48.25%   48.25%           
=============================================
  Files                96       96           
  Lines             11886    11886           
=============================================
  Hits               5735     5735           
  Misses             5516     5516           
  Partials            635      635           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

@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	89bf30c	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.