Bump fastlane to 2.235.0 and jwt to 3.2.0 (CVE-2026-45363)#663
Open
bjorkert wants to merge 1 commit into
Open
Conversation
jwt < 3.2.0 accepts attacker-forged tokens when an empty or nil key is used with HMAC algorithms (GHSA-c32j-vqhx-rx3x). fastlane 2.233.1 pinned jwt < 3, blocking the fix. fastlane 2.235.0 relaxes that to jwt < 4, allowing the upgrade to 3.2.0.
Collaborator
|
I think these 2 lines should be removed from Gemfile: I added them when they were needed for security issues with fastlane 2.233.1. When I bumped LoopKit/LoopWorkspace up to fastlane 2.234.0, they were no longer needed so I removed them. I tested |
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
2 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.
Resolves Dependabot alert #15 (GHSA-c32j-vqhx-rx3x / CVE-2026-45363).
jwt < 3.2.0accepts attacker-forged tokens when an empty or nil key is supplied to HMAC algorithms (HS256/HS384/HS512).fastlane 2.233.1had a hardjwt < 3upper bound that blocked the fix.fastlane 2.235.0relaxes that tojwt < 4, allowing the upgrade tojwt 3.2.0.