ruby-concurrency concurrent-ruby up to 1.3.6 ReadWriteLock#release_write_lock lock check
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 3.93- |
Summary
A vulnerability categorized as problematic has been discovered in ruby-concurrency concurrent-ruby up to 1.3.6. Impacted is the function Concurrent::ReadWriteLock#release_write_lock. The manipulation results in lock check.
This vulnerability is known as CVE-2026-54906. Attacking locally is a requirement. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in ruby-concurrency concurrent-ruby up to 1.3.6. It has been classified as problematic. Affected is the function Concurrent::ReadWriteLock#release_write_lock. The manipulation with an unknown input leads to a lock check vulnerability. CWE is classifying the issue as CWE-414. A product does not check to see if a lock is present before performing sensitive operations on a resource. This is going to have an impact on integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-54906 since 06/16/2026. The exploitability is told to be difficult. Local access is required to approach this attack. Technical details are known, but there is no available exploit.
Upgrading to version 1.3.7 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.6
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Lock checkCWE: CWE-414 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: concurrent-ruby 1.3.7
Timeline
06/16/2026 CVE reserved06/24/2026 Advisory disclosed
06/24/2026 VulDB entry created
06/24/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-54906 (🔒)
GCVE (CVE): GCVE-0-2026-54906
GCVE (VulDB): GCVE-100-373290
Entry
Created: 06/24/2026 18:34Changes: 06/24/2026 18:34 (67)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.