chore(deps): update module github.com/go-jose/go-jose/v4 to v4.1.4 [security] (release-v0.24)

[redhat-renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
github.com/go-jose/go-jose/v4	indirect	minor	v4.0.5 → v4.1.4

---

Go JOSE Panics in JWE decryption

CVE-2026-34986 / GHSA-78h2-9frx-2jm8

More information

Details

Impact

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

This code path is reachable from ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() followed by Decrypt() on the resulting object. Note that the parse functions take a list of accepted key algorithms. If the accepted key algorithms do not include any key wrapping algorithms, parsing will fail and the application will be unaffected.

This panic is also reachable by calling cipher.KeyUnwrap() directly with any ciphertext parameter less than 16 bytes long, but calling this function directly is less common.

Panics can lead to denial of service.

Fixed In

4.1.4 and v3.0.5

Workarounds

If the list of keyAlgorithms passed to ParseEncrypted() / ParseEncryptedJSON() / ParseEncryptedCompact() does not include key wrapping algorithms (those ending in KW), your application is unaffected.

If your application uses key wrapping, you can prevalidate to the JWE objects to ensure the encrypted_key field is nonempty. If your application accepts JWE Compact Serialization, apply that validation to the corresponding field of that serialization (the data between the first and second .).

Thanks

Thanks to Datadog's Security team for finding this issue.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/go-jose/go-jose/security/advisories/GHSA-78h2-9frx-2jm8
• https://nvd.nist.gov/vuln/detail/CVE-2026-34986
• https://github.com/go-jose/go-jose
• https://pkg.go.dev/github.com/go-jose/go-jose/v4#pkg-constants

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

go-jose/go-jose (github.com/go-jose/go-jose/v4)

v4.1.4

Compare Source

What's Changed

Fixes Panic in JWE decryption. See GHSA-78h2-9frx-2jm8

Full Changelog: go-jose/go-jose@v4.1.3...v4.1.4

v4.1.3

Compare Source

This release drops Go 1.23 support as that Go release is no longer supported. With that, we can drop x/crypto and no longer have any external dependencies in go-jose outside of the standard library!

This release fixes a bug where a critical b64 header was ignored if in an unprotected header. It is now rejected instead of ignored.

What's Changed

• Remove Go 1.23 support by @​mcpherrinm in #​205
• Reject JWS with an unprotected critical b64 header by @​mcpherrinm in #​210

Full Changelog: go-jose/go-jose@v4.1.2...v4.1.3

v4.1.2

Compare Source

What's Changed

go-jose v4.1.2 improves some documentation, errors, and removes the only 3rd-party dependency.

• Update go-jose documentation by @​mcpherrinm in #​198
• Remove dependency on testify by @​wardviaene in #​197
• Improve error message for invalid private keys by @​ProjectMutilation in #​195
• JWK unsupported error when unmarshalling by @​fprojetto in #​191
• Add JSONWebKey type to makeJWERecipient by @​alvarolivie in #​200
• testutils/assert: remove True, Nil, NotNil by @​jsha in #​202

New Contributors

• @​wardviaene made their first contribution in #​197
• @​fprojetto made their first contribution in #​191
• @​alvarolivie made their first contribution in #​200

Full Changelog: go-jose/go-jose@v4.1.1...v4.1.2

v4.1.1

Compare Source

What's Changed

• Drop go-cmp dependency by @​mcpherrinm in #​186
• jws: improve performance and allocations for ParseSignedCompact by @​drakkan in #​188
• Add missing quote to unknown curve message #​170 by @​sudhanvaghebbale in #​189
• Fix incorrect validation by @​ProjectMutilation in #​192
• Restore Go 1.23 compatibility by @​anuraaga in #​193

New Contributors

• @​drakkan made their first contribution in #​188
• @​sudhanvaghebbale made their first contribution in #​189
• @​ProjectMutilation made their first contribution in #​192
• @​anuraaga made their first contribution in #​193

Full Changelog: go-jose/go-jose@v4.1.0...v4.1.1

v4.1.0

Compare Source

What's Changed

• Document signatureAlgorithms argument by @​tgeoghegan in #​163
• Add custom error for unsupported JWS signature algorithms by @​beautifulentropy in #​181
• use stdlib pbkdf2 package on go 1.24 by @​kruskall in #​180
• The minimum supported Go version is now 1.24

New Contributors

• @​kruskall made their first contribution in #​180

Full Changelog: go-jose/go-jose@v4.0.5...v4.1.0

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[redhat-renovate-bot]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.22.7 -> 1.24.0

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-renovate-bot
Once this PR has been reviewed and has the lgtm label, please assign 0xfelix 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

[kubevirt-bot]

[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 0xfelix 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

[openshift-ci]

@redhat-renovate-bot: 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-tests	54d0b60	link	true	/test e2e-tests

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.