Is concurrent-ruby 0.1 vulnerable?
RubyGems · 2 releases from 0.1.0 to 0.1.1 · latest concurrent-ruby is 1.3.8 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. concurrent-ruby 0.1.1, the last 0.1 release, is affected by 3 known security advisories (1 high, 2 low), including CVE-2026-54904, CVE-2026-54906, CVE-2026-54905. Upgrade to 1.3.7 or later to fix all of them.
bundle update --conservative concurrent-ruby # Gemfile: '>= 1.3.7'Is your project on an affected concurrent-ruby?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting concurrent-ruby 0.1.1
Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption
- Affected
- <1.3.7
- Fixed in
- 1.3.7
Concurrent Ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
- Affected
- <1.3.7
- Fixed in
- 1.3.7
Concurrent Ruby : `AtomicReference#update` livelocks when the stored value is `Float::NAN`
- Affected
- <1.3.7
- Fixed in
- 1.3.7
Every concurrent-ruby 0.1.x release
Affected: 0.1.0 to 0.1.1. Latest concurrent-ruby: 1.3.8.
| Version | Known advisories |
|---|---|
| concurrent-ruby 0.1.1 | CVE-2026-54906, CVE-2026-54905, CVE-2026-54904 |
| concurrent-ruby 0.1.0 | CVE-2026-54906, CVE-2026-54905, CVE-2026-54904 |
Which of your client projects are still on concurrent-ruby 0.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact concurrent-ruby version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other concurrent-ruby versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.