CVE-2026-54906
CRITICALconcurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption
Title source: cnaDescription
concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLock#release_write_lock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running. Concurrent::ReadWriteLock#release_read_lock also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from 0 to -1, after which normal read acquisition raises Concurrent::ResourceLimitError. This is a synchronization correctness issue in the public Concurrent::ReadWriteLock API. This vulnerability is fixed in 1.3.7.
References (1)
Core 1
Core References
X_Refsource_Confirm x_refsource_confirm
https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-6wx8-w4f5-wwcr
Scores
CVSS v3
9.8
EPSS
0.0016
EPSS Percentile
5.7%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA SSVC
Vulnrichment
Exploitation
poc
Automatable
no
Technical Impact
partial
Details
CWE
CWE-414
CWE-667
Status
published
Products (2)
ruby-concurrency/concurrent-ruby
< 1.3.7
rubyconcurrency/concurrent_ruby
< 1.3.7
Published
Jun 24, 2026
Tracked Since
Jun 24, 2026