VAULT-40931: update jose2go to v1.7.0 on release/vault-1.16.x#168
Closed
ryancragun wants to merge 1 commit intorelease/vault-1.16.xfrom
Closed
VAULT-40931: update jose2go to v1.7.0 on release/vault-1.16.x#168ryancragun wants to merge 1 commit intorelease/vault-1.16.xfrom
ryancragun wants to merge 1 commit intorelease/vault-1.16.xfrom
Conversation
Signed-off-by: Ryan Cragun <me@ryan.ec>
fairclothjm
approved these changes
Nov 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Bump jose2go dependency to resolve GHSA-9mj6-hxhv-w67j
Design of Change
go getRelated Issues/Pull Requests
[ ] [CVE-2025-63811](GHSA-9mj6-hxhv-w67j)
Contributor Checklist
[ ] Add relevant docs to upstream Vault repository, or sufficient reasoning why docs won’t be added yet
My Docs PR Link
Example
[ ] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)
[ ] Backwards compatible
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.