Is concurrent-ruby 1.3 vulnerable?

RubyGems · 8 releases from 1.3.1 to 1.3.8 · latest concurrent-ruby is 1.3.8 · checked 18 Nov 2026

No known advisories in the last release

concurrent-ruby 1.3.8, the last 1.3 release, has no known advisories. 3 advisories affect earlier 1.3.x releases, so update to 1.3.8.

Update within 1.3:bundle update --conservative concurrent-ruby # Gemfile: '>= 1.3.8'

Is your project on an affected concurrent-ruby?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.3.x, affecting earlier releases

  • LowCVE-2026-54906GHSA-6wx8-w4f5-wwcr19 Jun 2026

    Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption

    Affected
    <1.3.7
    Fixed in
    1.3.7
  • LowCVE-2026-54905GHSA-wv3x-4vxv-whpp19 Jun 2026

    Concurrent Ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity

    Affected
    <1.3.7
    Fixed in
    1.3.7
  • HighCVE-2026-54904GHSA-h8w8-99g7-qmvj19 Jun 2026

    Concurrent Ruby : `AtomicReference#update` livelocks when the stored value is `Float::NAN`

    Affected
    <1.3.7
    Fixed in
    1.3.7

Every concurrent-ruby 1.3.x release

Affected: 1.3.1 to 1.3.6. 1.3.7 and later are not affected.

VersionKnown advisories
concurrent-ruby 1.3.8None
concurrent-ruby 1.3.7None
concurrent-ruby 1.3.6CVE-2026-54906, CVE-2026-54905, CVE-2026-54904
concurrent-ruby 1.3.5CVE-2026-54906, CVE-2026-54905, CVE-2026-54904
concurrent-ruby 1.3.4CVE-2026-54906, CVE-2026-54905, CVE-2026-54904
concurrent-ruby 1.3.3CVE-2026-54906, CVE-2026-54905, CVE-2026-54904
concurrent-ruby 1.3.2CVE-2026-54906, CVE-2026-54905, CVE-2026-54904
concurrent-ruby 1.3.1CVE-2026-54906, CVE-2026-54905, CVE-2026-54904

Which of your client projects are still on concurrent-ruby 1.3?

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.