Wrap-around Error Affecting ruby3.4-rails-8.1 package, versions <8.1.3-r7


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.15% (5th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-RUBY34RAILS81-17686695
  • published30 Jun 2026
  • disclosed24 Jun 2026

Introduced: 24 Jun 2026

CVE-2026-54905  (opens in a new tab)
CWE-128  (opens in a new tab)

How to fix?

Upgrade Chainguard ruby3.4-rails-8.1 to version 8.1.3-r7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ruby3.4-rails-8.1 package and not the ruby3.4-rails-8.1 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1