Advisory Database
  • Advisories
  • Dependency Scanning
  1. gem
  2. ›
  3. concurrent-ruby
  4. ›
  5. CVE-2026-54905

CVE-2026-54905: Concurrent Ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity

June 19, 2026

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.

References

  • github.com/advisories/GHSA-wv3x-4vxv-whpp
  • github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp
  • nvd.nist.gov/vuln/detail/CVE-2026-54905

Code Behaviors & Features

Detect and mitigate CVE-2026-54905 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 1.3.7

Fixed versions

  • 1.3.7

Solution

Upgrade to version 1.3.7 or above.

Impact 5.3 MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Learn more about CVSS

Weakness

  • CWE-128: Wrap-around Error

Source file

gem/concurrent-ruby/CVE-2026-54905.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sat, 20 Jun 2026 12:16:53 +0000.