Finding and attribution
After 32,768 reentrant read acquisitions, a per-thread count sets the bit interpreted as WRITE_LOCK_HELD; try_write_lock can return success without setting the global writer flag, so concurrent readers may continue.
Product: concurrent-ruby. AI system: depthfirst AI security agents (specific model not identified for this Ruby research). Team / organization: depthfirst / respective project maintainers.
CVE identifiers: CVE-2026-54905.
AI and human contribution (source account): depthfirst’s primary July 27, 2026 Ruby ecosystem report identifies CVE-2026-54905 as an issue uncovered in the research, and says its AI security agents analyzed the projects and validated each finding with a triggering input, reproduction script and evidence such as ASan output before manual review. The issue-specific section describes this exact vulnerability. The affected project maintainer advisory validates the vulnerability and fix. No specific model or per-case human/agent split is stated.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The maintainer advisory and CNA record provide public dates for CVE-2026-54905; the depthfirst account is dated 2026-07-27. The sources do not report exploitation in the wild or establish zero-day status.
Remediation status: fix documented. 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. This documents upstream package version guidance and does not establish downstream distribution patch state.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 24 Jun 2026. AI attribution dated 27 Jul 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Low · highest recorded score 2. Documented technical effects: other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-54905: CVSS 4.0 · 2 (Low) ·
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 CVE Program record · checked 17 Nov 2026.
CVE-2026-54905: other.
Prerequisites / affected scope: Code uses Concurrent::ReentrantReadWriteLock and one thread acquires the read lock at least 32,768 times before attempting the write lock. This breaks the lock’s mutual-exclusion guarantee; downstream data exposure or modification depends on application use and is not asserted here..
Exploitation evidence: The primary maintainer advisory documents the threshold and fix; no specific downstream exploit or in-the-wild use is reported.. Impact source · checked 17 Nov 2026.
Documented fix: 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. This documents upstream package version guidance and does not establish downstream distribution patch state.