Fix possible fix(deps): 2 vulnerable dependencies in Gemfile.lock - #77
Open
begininvoke wants to merge 1 commit into
Open
Fix possible fix(deps): 2 vulnerable dependencies in Gemfile.lock#77begininvoke 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.
Small change to
Gemfile.lock— a scan flagged the code below and it looked genuine. It is around line 33.The vulnerability arises from insufficient thread-ownership verification in concurrent-ruby’s ReadWriteLock, allowing any thread to release locks it does not own and causing incorrect internal counter manipulation. This leads to race conditions, data corruption, and potential denial of service via Concurrent::ResourceLimitError. Given the compromise of core concurrency primitives and application stability, it poses a CRITICAL risk.
Update concurrent-ruby to version 1.3.7 to address CVE‑2026‑54906 and CVE‑2026‑54904.
For reference: rule
CVE-2026-54906. Rated critical.I may well be missing context here — if the current code is deliberate, feel free to close this.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.