Fix possible fix(deps): 5 vulnerable dependencies in Gemfile.lock - #331
Open
begininvoke wants to merge 1 commit into
Open
Fix possible fix(deps): 5 vulnerable dependencies in Gemfile.lock#331begininvoke wants to merge 1 commit into
begininvoke wants to merge 1 commit into
Conversation
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.
This changes
Gemfile.lockto address something a scan flagged. It is around line 20.The project pins concurrent-ruby at version 1.3.6, which contains a critical synchronization flaw (CVE-2026-54906). The ReadWriteLock API can be abused to release another thread's write lock or to corrupt the read‑counter, potentially allowing multiple writers to run concurrently or causing ResourceLimitError exceptions. This breaks thread‑safety and can lead to data races, corruption, or denial‑of‑service. Because the issue is exploitable in any environment that uses the lock, the risk is Critical. The fix is to upgrade concurrent‑ruby to version 1.3.7 or newer, where the lock release methods correctly verify ownership.
Updated vulnerable dependencies to versions that fix the reported CVEs while preserving existing constraints.
For reference: rule
CVE-2026-54906. Rated critical.I do not know the codebase, so please check the change fits how the rest of it works. Happy to adjust it or close this if the reasoning is off.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.