CVE-2026-54905 json
concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
published 2026-06-19 4 mo ago modified 2026-10-25 14 d ago also GHSA-wv3x-4vxv-whpp , EUVD-2026-39000
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- rubygems concurrent-ruby 1.3.7
- rubyconcurrency concurrent_ruby 1.3.7
- ruby-concurrent Debian 14 1.3.7-1
debian advisories DEBIAN-CVE-2026-54905
- rubygem-concurrent-ruby Azure Linux 3.0 1.3.7-1
azure linux advisories AZL-91290
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-54905 updated cvss 4.7
concurrent-ruby: Concurrent-ruby: Incorrect write lock granting leading to broken mutual exclusion
-
Red Hat 3scale API Management Platform 2 3scale-amp21/zync, 3scale-amp22/zync, 3scale-amp21/system, 3scale-amp22/system, 3scale-amp21/backend, 3scale-amp22/backend, +9 more Red Hat OpenStack Platform 17.1 rubygem-concurrent-ruby Red Hat Satellite 6 rubygem-concurrent-rubyaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.0 | CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 2.0 | CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | concurrent-ruby | <1.3.7 |
1.3.7 |
Affected products
- ruby-concurrency concurrent-ruby
Classification
- Weakness
-
- CWE-128 Wrap-around Error
References
-
github.com
/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp
exploit, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-54905
advisory
-
github.com
/ruby-concurrency/concurrent-ruby
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/concurrent-ruby/CVE-2026-54905.yml
web
-
cve.org
/CVERecord/SearchResults?query=CVE-2026-54905
web
Sources
- CVE List CVE-2026-54905
- GitHub Advisory GHSA-wv3x-4vxv-whpp
- NVD CVE-2026-54905
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.