ListedExploitable · Confirmed
concurrent-ruby: Concurrent Ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
It is on record here. It does not touch anything Phylax follows closely.
Does it affect what I run?
concurrent-ruby (RubyGems)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- concurrent-ruby (RubyGems): every version, before 1.3.7
The fix
concurrent-ruby (RubyGems) fixed in 1.3.7
bundlerbundle update --conservative concurrent-rubyCheck what is installedbundle info concurrent-rubyPaste into Cursor, Lovable or Claude CodeUpgrade the RubyGems dependency concurrent-ruby to 1.3.7 or the nearest later release, to fix CVE-2026-54905. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "Listed".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))