[dependabot]

Bumps github.com/go-jose/go-jose/v4 from 4.1.4 to 4.1.6.

Release notes

Sourced from github.com/go-jose/go-jose/v4's releases.

v4.1.6

Fixed Security Issues

This release contains a fix for GHSA-mgcc-cww5-fp2q

Breaking Changes

The fix for GHSA-mgcc-cww5-fp2q involves capping the size of the RSA modulus of keys accepted by JWK parsing. This limit is 4096 bits. If you need this to be higher, set MaxRSAModulusBits before performing any JWK parsing.

Changed

• Reject mismatched JWE CEK lengths by @​akshithg in go-jose/go-jose#266
• Add a tests containerfile and threat model by @​mcpherrinm in go-jose/go-jose#300
• Fix error message for future issued tokens by @​inahga in go-jose/go-jose#303

Full Changelog: go-jose/go-jose@v4.1.5...v4.1.6

v4.1.5

Fixed security issues

• cipher/cbc_hmac: don't panic on empty ciphertext (#292)
• cipher/cbc_hmac: don't panic on invalid key (#291)
• json: limit stack depth (#290)
• jwt: reject out-of-range NumericDate values (#278)
• Check alg against pubkey curve during verify. (#293)
• Reject malformed Ed25519 JWKs (#250)
• jws: choose verification key per-signature (#243)

Breaking Changes

In #226, we un-exported jose.RandReader. This was used to be able to stub out the randomness function in tests, but is ignored as of Go 1.26 in some APIs, so no longer serves a useful function.

Changed

• Verify OpaqueSigner's Public() return is public (#260)
• jws: skip signature on ErrJWKSKidNotFound (#248)
• Handle JWE JSON without protected header (#240)
• jws: don't strip internal whitespace before parsing JSON (#239)
• jws: fewer calls to OpaqueSigner.Public() (#224)
• Return a specific error when parsing empty string (#216)
• Reject typed nil at Verify time (#285)

Commits

• a0111f8 Merge commit from fork
• dd39a41 Fix error message for future issued tokens (#303)
• 13b7118 Add a tests containerfile and threat model (#300)
• 25b55fe Reject mismatched JWE CEK lengths (#266)
• b10771e Reject typed nil at Verify time
• 56f3866 Check alg against pubkey curve during verify. (#293)
• 74114c2 cipher/cbc_hmac: don't panic on empty ciphertext (#292)
• 6b364f3 cipher/cbc_hmac: don't panic on invalid key (#291)
• a31af25 json: limit stack depth (#290)
• 7f5beb3 jwt: reject out-of-range NumericDate values (#278)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[gopherbot]

This PR (HEAD: 4c952aa) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/build/+/858001.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.