CVE-2026-54906: concurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption

criticalCVSS 9.8CVE-2026-54906

CSIRTS triage

vendor: concurrent-ruby product: concurrent-rubyOther

What: The vulnerability allows incorrect thread write releases and read-release counter corruption.
Who is affected: Users of the concurrent-ruby library.
Urgency: Remediation is critical due to the high severity and potential for exploitation.
Action: Upgrade to the patched version of concurrent-ruby.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch concurrent-ruby

Get an email when a new concurrent-ruby advisory drops — max one per day, one-click unsubscribe.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: critical — CVSS 9.8
Published: 2026-06-09
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54906

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-549060.16% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 6% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-54906	coverage & exploitation status	NVD · CVE.org

Recent advisories for concurrent-ruby

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

mediumCVE-2026-54905: concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without excl…msrc · 2026-06-09