Skip to content

Update vulnerable dependencies [SECURITY] (patch)#2671

Merged
pulumi-renovate[bot] merged 1 commit intomasterfrom
renovate/patch-security
Apr 3, 2026
Merged

Update vulnerable dependencies [SECURITY] (patch)#2671
pulumi-renovate[bot] merged 1 commit intomasterfrom
renovate/patch-security

Conversation

@pulumi-renovate
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
github.com/go-jose/go-jose/v3 indirect patch v3.0.4 -> v3.0.5
github.com/go-jose/go-jose/v4 indirect patch v4.1.3 -> v4.1.4

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/v3)

v3.0.5

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - Monday through Friday ( * * * * 1-5 ) (UTC).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@pulumi-renovate pulumi-renovate bot added dependencies Pull requests that update a dependency file impact/no-changelog-required This issue doesn't require a CHANGELOG update labels Apr 3, 2026
@pulumi-renovate pulumi-renovate bot enabled auto-merge (squash) April 3, 2026 09:44
@pulumi-renovate pulumi-renovate bot merged commit 765e13b into master Apr 3, 2026
27 checks passed
@pulumi-renovate pulumi-renovate bot deleted the renovate/patch-security branch April 3, 2026 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file impact/no-changelog-required This issue doesn't require a CHANGELOG update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants