{"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-54906 exists.","fix":"Upgrade concurrent-ruby to 1.3.7 or later.","what":"CVE-2026-54906 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-54906 and fix it if it is affected.\n\nWhat it is: CVE-2026-54906 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-54906 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-54906/ (Markdown: https://insights.sbomify.com/CVE-2026-54906/index.md)","id":"CVE-2026-54906","markdown":"https://insights.sbomify.com/CVE-2026-54906/index.md","name":"CVE-2026-54906","record":{"aliases":["AZL-91287","CLEANSTART-2026-JE87878","CLEANSTART-2026-RJ92739","DEBIAN-CVE-2026-54906","GHSA-6wx8-w4f5-wwcr","MINI-29jf-g952-x29m","MINI-39qr-2wcq-mxr9","MINI-4pgg-xwpw-m594","MINI-56jv-fq6c-vx2p","MINI-87cp-9hm8-f58p","MINI-9hw4-hvqg-w8r7","MINI-9mc2-h329-wg9r","MINI-j3rg-jr7w-cprh","MINI-jmj4-gpx9-fg2h","MINI-jrhp-97g8-f9hw","MINI-mjxp-2h4v-9gp8","MINI-q37q-3295-vrqv","MINI-qpgf-p9r5-qh6j","MINI-r25m-vgq3-84g7","MINI-rhrm-fxch-x5jw","MINI-v2xv-pqf9-g62w","MINI-wj6m-9j3x-vpmj","MINI-xxcv-m5vq-fxm3","UBUNTU-CVE-2026-54906"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby concurrency library","requires_auth":"none","summary":"Attackers can corrupt lock state or cause denial of service by improperly releasing locks in the concurrent-ruby library.","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.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-667","name":"Improper Locking"},{"id":"CWE-414","name":"Missing Lock Check"}],"description":"concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLock#release_write_lock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running. Concurrent::ReadWriteLock#release_read_lock also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from 0 to -1, after which normal read acquisition raises Concurrent::ResourceLimitError. This is a synchronization correctness issue in the public Concurrent::ReadWriteLock API. 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: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption","id":"CVE-2026-54906","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":"Caddy Proxy Manager: Registrations enabled by default allows creating users with \"user\" permission","id":"CVE-2026-54907"},"packages":[{"ecosystem":"RubyGems","fixed":["1.3.7"],"introduced":["0"],"last_affected":[],"package":"concurrent-ruby","purl":null,"source":"GHSA-6wx8-w4f5-wwcr"},{"ecosystem":"RubyGems","fixed":["1.3.7"],"introduced":["0"],"last_affected":[],"package":"concurrent-ruby","purl":"pkg:gem/concurrent-ruby","source":"GHSA-6wx8-w4f5-wwcr"}],"prev":{"headline":"concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity","id":"CVE-2026-54905"},"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,"headline":"concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity","id":"CVE-2026-54905","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":"Attackers can corrupt lock state or cause denial of service by improperly releasing locks in the concurrent-ruby library.","url":"https://insights.sbomify.com/CVE-2026-54906/"}