{
  "id": "cve-2026-54905",
  "title": "concurrent-ruby reentrant reader count crosses write-lock flag",
  "product": "concurrent-ruby",
  "ai_system": "depthfirst AI security agents (specific model not identified for this Ruby research)",
  "organization": "depthfirst / respective project maintainers",
  "summary": "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.",
  "ai_role": "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.",
  "disclosure_date": "2026-06-24",
  "ai_attribution_date": "2026-07-27",
  "classification": "disclosure",
  "classification_note": "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.",
  "cves": [
    "CVE-2026-54905"
  ],
  "source_url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp",
  "ai_source_url": "https://depthfirst.com/research/behind-the-gitlab-rce-a-depthfirst-journey-into-the-ruby-ecosystem",
  "advisory_url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp",
  "remediation": "fix documented",
  "remediation_note": "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.",
  "checked_date": "2026-11-17",
  "impacts": [
    {
      "cves": [
        "CVE-2026-54905"
      ],
      "consequences": [
        "other"
      ],
      "conditions": "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": "The primary maintainer advisory documents the threshold and fix; no specific downstream exploit or in-the-wild use is reported.",
      "source_url": "https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp",
      "checked_date": "2026-11-17"
    }
  ],
  "cvss": [
    {
      "cve": "CVE-2026-54905",
      "version": "4.0",
      "score": 2,
      "vector": "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",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/54xxx/CVE-2026-54905.json",
      "source_name": "CNA CVE Program record",
      "checked_date": "2026-11-17"
    }
  ]
}
