chore(deps): Update jsonwebtoken requirement from 9.2 to 10.3#767
Open
jasonhernandez wants to merge 1 commit into
Open
chore(deps): Update jsonwebtoken requirement from 9.2 to 10.3#767jasonhernandez wants to merge 1 commit into
jasonhernandez wants to merge 1 commit into
Conversation
jsonwebtoken prior to 10.3.0 is affected by CVE-2026-25537 (type confusion in claim validation). jsonwebtoken 10 requires selecting a crypto backend via feature, so this adds jwt-rust-crypto (in default features, preserving existing behavior) and jwt-aws-lc-rs (opt-in). Raises MSRV to 1.85. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jasonhernandez
changed the title
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
1 participant
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.
Motivation
I noticed that reqsign 0.16.x is optionally pulling in a version of jsonwebtoken flagged with a CVE: CVE-2026-25537. This doesn't have direct security implications because reqsign isn't using vulnerable code paths. This just helps clear up some vulnerability scanner noise for anyone pulling in this version of reqsign.
If you're interested in making a small dependency bump on the v0.16.x version line, this is a tiny patch to do so!
If not, feel free to close this. Thanks for taking a look in either case!