Wrap-around Error Affecting ruby3.2-fluentd-kubernetes-daemonset-1.19 package, versions <1.19.2.1.1-r5
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-WOLFILATEST-RUBY32FLUENTDKUBERNETESDAEMONSET119-17812494
- published4 Jul 2026
- disclosed24 Jun 2026
Introduced: 24 Jun 2026
CVE-2026-54905 (opens in a new tab)How to fix?
Upgrade Wolfi ruby3.2-fluentd-kubernetes-daemonset-1.19 to version 1.19.2.1.1-r5 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ruby3.2-fluentd-kubernetes-daemonset-1.19 package and not the ruby3.2-fluentd-kubernetes-daemonset-1.19 package as distributed by Wolfi.
See How to fix? for Wolfi 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.