CVE-2026-54905
concurrent-ruby is a modern concurrency tools for Ruby. Prior to …
concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock after one thread acquires the read lock 32,768 times. The lock stores a thread's local read and write hold counts in one integer. The low 15 bits are used for the read hold count, and bit 15 is used as WRITE_LOCK_HELD. After 32,768 reentrant read acquisitions, the local read count crosses into the write-lock bit. try_write_lock then treats the thread as already holding a write lock and returns true without setting the global RUNNING_WRITER bit. This breaks the core mutual-exclusion guarantee: the caller is told it has a write lock, but other threads can still hold or acquire read locks at the same time. This vulnerability is fixed in 1.3.7.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp
- github.com/advisories/GHSA-wv3x-4vxv-whpp
- nvd.nist.gov/vuln/detail/CVE-2026-54905
- github.com/rubysec/ruby-advisory-db/blob/master/gems/concurrent-ruby/CVE-2026-54905.yml
- www.cve.org/CVERecord/SearchResults?query=CVE-2026-54905
- nvd.nist.gov/vuln/detail/CVE-2026-54905
- cve.org/CVERecord?id=CVE-2026-54905
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.