Skip to content

update(deps): update module github.com/go-jose/go-jose/v4 to v4.1.4 [security]#291

Open
CodesphereBot wants to merge 1 commit intomainfrom
renovate/go-github.com-go-jose-go-jose-v4-vulnerability
Open

update(deps): update module github.com/go-jose/go-jose/v4 to v4.1.4 [security]#291
CodesphereBot wants to merge 1 commit intomainfrom
renovate/go-github.com-go-jose-go-jose-v4-vulnerability

Conversation

@CodesphereBot
Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Change Age Confidence
github.com/go-jose/go-jose/v4 v4.1.3 -> v4.1.4 age confidence

GitHub Vulnerability Alerts

CVE-2026-34986

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

Go JOSE thanks Datadog's Security team for finding this issue.


Release Notes

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

v4.1.4

Compare Source


Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@CodesphereBot CodesphereBot enabled auto-merge (squash) April 3, 2026 05:20
@CodesphereBot CodesphereBot force-pushed the renovate/go-github.com-go-jose-go-jose-v4-vulnerability branch from 96cd4c3 to ce9a1bf Compare April 3, 2026 05:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant