concurrent-ruby vulnerabilities

Modern concurrency tools including agents, futures, promises, thread pools, actors, supervisors, and more. Inspired by Erlang, Clojure, Go, JavaScript, actors, and classic concurrency patterns.

Registry
RubyGems
Latest
1.3.8
License
MIT

3 known advisories

The latest version, 1.3.8, is not affected by any of them. Projects on older versions may be.

Update to the latest version: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

Security advisories for concurrent-ruby

  • 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

Is your concurrent-ruby version vulnerable?

Which of your client projects still run an old concurrent-ruby?

NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other RubyGems packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.