{"answers":{"affected":"2 open source packages ship an affected version, including concurrent-ruby. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54905 exists.","fix":"Upgrade concurrent-ruby to 1.3.7 or later.","what":"CVE-2026-54905 is a low-severity vulnerability in ruby-concurrency concurrent-ruby, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54905 and fix it if it is affected.\n\nWhat it is: CVE-2026-54905 is a low-severity vulnerability in ruby-concurrency concurrent-ruby, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54905 exists.\n\nAffected packages and fixed versions:\n- concurrent-ruby (RubyGems): affected all versions; fixed in 1.3.7\n- concurrent-ruby (RubyGems): affected all versions; fixed in 1.3.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54905/ (Markdown: https://insights.sbomify.com/CVE-2026-54905/index.md)","id":"CVE-2026-54905","markdown":"https://insights.sbomify.com/CVE-2026-54905/index.md","name":"CVE-2026-54905","record":{"aliases":["AZL-91290","CLEANSTART-2026-CH23308","CLEANSTART-2026-VX25818","DEBIAN-CVE-2026-54905","GHSA-wv3x-4vxv-whpp","MINI-485g-xhv3-g79h","MINI-59pm-452g-j8r3","MINI-6c59-gr25-78f6","MINI-6v8p-9g89-8x8x","MINI-7mmf-3r64-v9wr","MINI-8r3f-chcf-3m68","MINI-cpg5-2q8x-vm25","MINI-g4rx-2xwj-7p47","MINI-g9qq-753f-q3cx","MINI-gh2j-vm93-h5g4","MINI-h8x8-rgmx-9x66","MINI-ppp2-v9gf-6x5x","MINI-prh8-ghfv-7h83","MINI-qwwm-wwrq-8j83","MINI-v324-75xr-r22h","MINI-vp6f-p4mw-w5f9","MINI-vrpf-45q5-x8g9","MINI-wq42-fq77-87pq","UBUNTU-CVE-2026-54905"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby concurrency library","requires_auth":"low_privilege","summary":"An integer overflow in concurrent-ruby allows a thread to bypass write lock exclusivity, potentially leading to data corruption or race conditions.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"concurrent_ruby","vendor":"rubyconcurrency"}],"cvss":{"score":2,"severity":"low","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-128","name":"Wrap-around Error"}],"description":"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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity","id":"CVE-2026-54905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"concurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption","id":"CVE-2026-54906"},"packages":[{"ecosystem":"RubyGems","fixed":["1.3.7"],"introduced":["0"],"last_affected":[],"package":"concurrent-ruby","purl":null,"source":"GHSA-wv3x-4vxv-whpp"},{"ecosystem":"RubyGems","fixed":["1.3.7"],"introduced":["0"],"last_affected":[],"package":"concurrent-ruby","purl":"pkg:gem/concurrent-ruby","source":"GHSA-wv3x-4vxv-whpp"}],"prev":{"headline":"concurrent-ruby: `AtomicReference#update` livelocks when the stored value is `Float::NAN`","id":"CVE-2026-54904"},"products":["concurrent-ruby"],"published":"2026-06-24","related":[{"cvss_score":8.2,"headline":"concurrent-ruby: `AtomicReference#update` livelocks when the stored value is `Float::NAN`","id":"CVE-2026-54904","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":2.1,"headline":"concurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption","id":"CVE-2026-54906","kev_date_added":null,"published":"2026-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["ruby-concurrency"]},"summary":"An integer overflow in concurrent-ruby allows a thread to bypass write lock exclusivity, potentially leading to data corruption or race conditions.","url":"https://insights.sbomify.com/CVE-2026-54905/"}