Vulnerability Details CVE-2026-54906
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.002
EPSS Ranking 5.6%
CVSS Severity
CVSS v3 Score 9.8
Products affected by CVE-2026-54906
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.0.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.0.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.1.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.1.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.2.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.2.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.2.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.3.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.3.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.3.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.4.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.4.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.5.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.6.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.6.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.7.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.7.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.8.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.9.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.9.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:0.9.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.0.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.0.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.0.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.0.3
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.0.4
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.0.5
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.10
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.3
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.4
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.5
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.6
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.7
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.8
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.1.9
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.2.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.2.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.2.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.2.3
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.0
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.1
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.2
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.3
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.4
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.5
-
cpe:2.3:a:rubyconcurrency:concurrent_ruby:1.3.6