OCPBUGS-84391: Bump go-jose to v4.1.4

[jkaurredhat]

Summary

Update github.com/go-jose/go-jose/v4 from v4.1.3 to v4.1.4 to address CVE-2026-34986.

CVE Details

• CVE-2026-34986: Go JOSE Denial of Service via crafted JSON Web Encryption (JWE) object
• GHSA: GHSA-7ww6-75fj-jcj7
• Component: JSON Web Encryption (JWE) decryption
• Patched version: v4.1.4

Vulnerability Description

Decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key.

Changes

• Bump github.com/go-jose/go-jose/v4 from v4.1.3 to v4.1.4
• Update vendor/ directory

[openshift-ci-robot]

@jkaurredhat: This pull request references Jira Issue OCPBUGS-84391, 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-84391 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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:

Summary

Update github.com/go-jose/go-jose/v4 from v4.1.3 to v4.1.4 to address CVE-2026-34986.

CVE Details

• CVE-2026-34986: Go JOSE Denial of Service via crafted JSON Web Encryption (JWE) object
• GHSA: GHSA-7ww6-75fj-jcj7
• Component: JSON Web Encryption (JWE) decryption
• Patched version: v4.1.4

Vulnerability Description

Decrypting a JSON Web Encryption (JWE) object will panic if the alg field indicates a key wrapping algorithm (one ending in KW) and the encrypted_key field is empty. The panic happens when cipher.KeyUnwrap() attempts to allocate a slice with a zero or negative length based on the length of the encrypted_key.

Changes

• Bump github.com/go-jose/go-jose/v4 from v4.1.3 to v4.1.4
• Update vendor/ directory

Test Plan

• Build succeeds
• Existing tests pass
• No functional changes (dependency update only)

Related: OCPBUGS-84391

🤖 Generated with Claude Code

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: 920941b7-cef5-485d-92f3-74b7dd2563e5

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

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[jkaurredhat]

/retest-required

[openshift-ci]

@jkaurredhat: all tests passed!

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.