VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

concurrent-ruby: vulnerability history, versions and safety

concurrent-ruby is a package in the RubyGems ecosystem. Vulert records 3 vulnerabilities for it across 77 releases, first recorded in Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 19 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all concurrent-ruby vulnerabilities

Vulert verdict on concurrent-ruby 1.3.8 i

Updated on 23 Oct 2026

Good news: 1.3.8, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 1.3.8 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.3.8 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.3.8 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 19 Jun 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Stars 5,836 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for concurrent-ruby, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.3.8 19 Jul 2026 none MIT — Details →
1.3.7 16 Jun 2026 none MIT — Details →
1.3.6 13 Dec 2025 H1 L2 MIT Yes Details →
1.3.5 15 Jan 2025 H1 L2 MIT Yes Details →
1.3.4 10 Aug 2024 H1 L2 MIT Yes Details →
1.3.3 09 Jun 2024 H1 L2 MIT Yes Details →
1.3.2 07 Jun 2024 H1 L2 MIT Yes Details →
1.3.1 29 May 2024 H1 L2 MIT Yes Details →
1.3.1.pre 29 May 2024 H1 L2 MIT Yes Details →
1.2.3 16 Jan 2024 H1 L2 MIT Yes Details →
1.2.2 24 Feb 2023 H1 L2 MIT Yes Details →
1.2.1 24 Feb 2023 H1 L2 MIT Yes Details →
1.2.0 23 Jan 2023 H1 L2 MIT Yes Details →
1.1.10 22 Mar 2022 H1 L2 MIT Yes Details →
1.1.9 05 Jun 2021 H1 L2 MIT Yes Details →
1.1.8 20 Jan 2021 H1 L2 MIT Yes Details →
1.1.7 08 Aug 2020 H1 L2 MIT Yes Details →
1.1.6 10 Feb 2020 H1 L2 MIT Yes Details →
1.1.6.pre1 26 Jan 2020 H1 L2 MIT Yes Details →
1.1.5 11 Mar 2019 H1 L2 MIT Yes Details →
1.1.4 15 Dec 2018 H1 L2 MIT Yes Details →
1.1.3 07 Nov 2018 H1 L2 MIT Yes Details →
1.1.2 06 Nov 2018 H1 L2 MIT Yes Details →
1.1.1 05 Nov 2018 H1 L2 MIT Yes Details →
1.1.0.pre2 18 Sep 2018 H1 L2 MIT Yes Details →
1.1.0.pre1 15 Aug 2018 H1 L2 MIT Yes Details →
1.0.5 26 Feb 2017 H1 L2 MIT Yes Details →
1.0.4 27 Dec 2016 H1 L2 MIT Yes Details →
1.0.3 17 Dec 2016 H1 L2 MIT Yes Details →
1.0.3.pre3 23 Jun 2016 H1 L2 MIT Yes Details →
1.0.2 02 May 2016 H1 L2 MIT Yes Details →
1.0.1 27 Feb 2016 H1 L2 MIT Yes Details →
1.0.0 13 Nov 2015 H1 L2 MIT Yes Details →
1.0.0.pre5 05 Nov 2015 H1 L2 MIT Yes Details →
0.9.2 04 Nov 2015 H1 L2 MIT Yes Details →
1.0.0.pre4 08 Oct 2015 H1 L2 MIT Yes Details →
1.0.0.pre3 30 Sep 2015 H1 L2 MIT Yes Details →
1.0.0.pre2 19 Sep 2015 H1 L2 MIT Yes Details →
1.0.0.pre1 19 Aug 2015 H1 L2 MIT Yes Details →
0.9.1 09 Aug 2015 H1 L2 MIT Yes Details →
0.9.0 10 Jul 2015 H1 L2 MIT Yes Details →
0.9.0.pre3 22 Jun 2015 H1 L2 MIT Yes Details →
0.9.0.pre2 08 Jun 2015 H1 L2 MIT Yes Details →
0.8.0 25 Jan 2015 H1 L2 MIT Yes Details →
0.7.2 25 Jan 2015 H1 L2 MIT Yes Details →
0.8.0.pre2 15 Jan 2015 H1 L2 MIT Yes Details →
0.8.0.pre1 18 Dec 2014 H1 L2 MIT Yes Details →
0.7.1 05 Dec 2014 H1 L2 MIT Yes Details →
0.7.0 13 Aug 2014 H1 L2 MIT Yes Details →
0.7.0.rc2 30 Jul 2014 H1 L2 MIT Yes Details →
0.7.0.rc1 27 Jun 2014 H1 L2 MIT Yes Details →
0.7.0.rc0 18 Jun 2014 H1 L2 MIT Yes Details →
0.6.1 15 Jun 2014 H1 L2 MIT Yes Details →
0.6.0 26 May 2014 H1 L2 MIT Yes Details →
0.6.0.pre.2 13 May 2014 H1 L2 MIT Yes Details →
0.6.0.pre.1 08 Apr 2014 H1 L2 MIT Yes Details →
0.5.0 16 Mar 2014 H1 L2 MIT Yes Details →
0.5.0.pre.1 10 Mar 2014 H1 L2 MIT Yes Details →
0.4.1 04 Feb 2014 H1 L2 MIT Yes Details →
0.4.0 07 Jan 2014 H1 L2 MIT Yes Details →
0.3.2 08 Nov 2013 H1 L2 MIT Yes Details →
0.3.1 07 Nov 2013 H1 L2 MIT Yes Details →
0.3.1.pre.2 06 Nov 2013 H1 L2 MIT Yes Details →
0.3.1.pre.1 03 Nov 2013 H1 L2 MIT Yes Details →
0.3.0 18 Oct 2013 H1 L2 MIT Yes Details →
0.3.0.pre.3 17 Oct 2013 H1 L2 MIT Yes Details →
0.3.0.pre.2 13 Oct 2013 H1 L2 MIT Yes Details →
0.3.0.pre.1 10 Oct 2013 H1 L2 MIT Yes Details →
0.2.2 20 Aug 2013 H1 L2 MIT Yes Details →
0.2.1 20 Aug 2013 H1 L2 MIT Yes Details →
0.2.0 20 Aug 2013 H1 L2 MIT Yes Details →
0.1.1.pre.5 15 Aug 2013 H1 L2 MIT Yes Details →
0.1.1.pre.4 14 Aug 2013 H1 L2 MIT Yes Details →
0.1.1.pre.3 12 Aug 2013 H1 L2 MIT Yes Details →
0.1.1.pre.2 08 Aug 2013 H1 L2 MIT Yes Details →
0.1.1.pre.1 06 Aug 2013 H1 L2 MIT Yes Details →
0.1.1 29 Jul 2013 H1 L2 MIT Yes Details →
0.1.0 25 Jul 2013 H1 L2 MIT Yes Details →
0.0.1 23 Jul 2013 H1 L2 MIT Yes Details →

All 79 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for concurrent-ruby

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54904: Concurrent Ruby AtomicReference Livelock Due to Float::NAN 8.2 high 1.3.7 19 Jun 2026
CVE-2026-54906: Concurrent Ruby - Incorrect Thread Handling in ReadWriteLock 2.1 low 1.3.7 19 Jun 2026
CVE-2026-54905: Concurrent Ruby ReentrantReadWriteLock Read-Count Overflow Vulnerability 2.0 low 1.3.7 19 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About concurrent-ruby

Is concurrent-ruby safe to use?

Vulert records 3 vulnerabilities for concurrent-ruby in RubyGems: 0 critical, 1 high, 0 medium and 2 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is concurrent-ruby's Vulert package health score?

Vulert scores concurrent-ruby 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of concurrent-ruby affected?

No. 1.3.8, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of concurrent-ruby should I use?

1.3.8 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does concurrent-ruby have?

3 vulnerabilities are recorded for concurrent-ruby in the RubyGems ecosystem: 0 critical, 1 high, 0 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new concurrent-ruby vulnerabilities disclosed?

3 vulnerabilities were recorded for concurrent-ruby in the last 12 months, and the oldest entry in this database dates to 19 Jun 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of concurrent-ruby are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor concurrent-ruby for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the concurrent-ruby version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.