CVE-2026-54905

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock after one thread acquires the read lock 32,768 times. The lock stores a thread's local read and write hold counts in one integer. The low 15 bits are used for the read hold count, and bit 15 is used as WRITE_LOCK_HELD. After 32,768 reentrant read acquisitions, the local read count crosses into the write-lock bit. try_write_lock then treats the thread as already holding a write lock and returns true without setting the global RUNNING_WRITER bit. This breaks the core mutual-exclusion guarantee: the caller is told it has a write lock, but other threads can still hold or acquire read locks at the same time. This vulnerability is fixed in 1.3.7.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

`ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity · Advisory · ruby-concurrency/concurrent-ruby · GitHub

https://github.com/ruby-concurrency/concurrent-ruby/security/advisories/GHSA-wv3x-4vxv-whpp

Vendor Advisories for CVE-2026-54905(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-concurrent1.1.6+dfsg-3 ... 1.3.8-1 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-concurrent1.1.6+dfsg-5 ... 1.3.8-1 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-concurrent1.3.5-1 ... 1.3.8-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-concurrent1.3.5-1, 1.3.6-11.3.7-1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
concurrent-ruby0.0.1 ... 1.3.6 (77 versions)1.3.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 123 total refreshes for this CVE.

  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-22 23:37 UTCEG score recompute
  3. 2026-08-22 23:37 UTCVendor advisory
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 07:20 UTCEG score recompute
  6. 2026-08-21 07:20 UTCVendor advisory
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 07:59 UTCVendor advisory
  9. 2026-08-19 07:00 UTCEG score recompute
  10. 2026-08-19 07:00 UTCVendor advisory
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 15:27 UTCEG score recompute
  13. 2026-08-17 15:27 UTCVendor advisory
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 16:16 UTCEG score recompute
  16. 2026-08-16 16:16 UTCVendor advisory
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 17:06 UTCEG score recompute
  20. 2026-08-15 17:06 UTCVendor advisory
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 17:56 UTCEG score recompute
  23. 2026-08-14 17:56 UTCVendor advisory
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 18:47 UTCVendor advisory
Show 75 more
  1. 2026-08-12 18:57 UTCEG score recompute
  2. 2026-08-12 18:57 UTCVendor advisory
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 19:48 UTCEG score recompute
  5. 2026-08-11 19:48 UTCVendor advisory
  6. 2026-08-09 21:29 UTCEG score recompute
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-08 22:21 UTCEG score recompute
  9. 2026-08-08 22:21 UTCVendor advisory
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-07 23:12 UTCEG score recompute
  12. 2026-08-07 00:04 UTCEG score recompute
  13. 2026-08-07 00:04 UTCVendor advisory
  14. 2026-08-06 13:47 UTCEPSS rescore
  15. 2026-08-06 00:54 UTCEG score recompute
  16. 2026-08-06 00:54 UTCVendor advisory
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-05 01:45 UTCEG score recompute
  19. 2026-08-05 01:45 UTCVendor advisory
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 10:39 UTCEPSS rescore
  22. 2026-08-04 02:35 UTCEG score recompute
  23. 2026-08-04 02:35 UTCVendor advisory
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-03 03:26 UTCVendor advisory
  26. 2026-08-02 04:11 UTCEG score recompute
  27. 2026-08-02 04:11 UTCVendor advisory
  28. 2026-08-02 02:27 UTCEPSS rescore
  29. 2026-08-01 05:01 UTCEG score recompute
  30. 2026-08-01 05:01 UTCVendor advisory
  31. 2026-08-01 04:16 UTCEPSS rescore
  32. 2026-07-31 03:47 UTCEG score recompute
  33. 2026-07-31 03:47 UTCVendor advisory
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 02:54 UTCEG score recompute
  36. 2026-07-30 02:54 UTCVendor advisory
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-29 01:33 UTCEG score recompute
  39. 2026-07-29 01:33 UTCVendor advisory
  40. 2026-07-28 15:37 UTCEPSS rescore
  41. 2026-07-27 18:02 UTCVendor advisory
  42. 2026-07-26 16:47 UTCEG score recompute
  43. 2026-07-26 16:47 UTCVendor advisory
  44. 2026-07-25 14:18 UTCEPSS rescore
  45. 2026-07-24 14:18 UTCEPSS rescore
  46. 2026-07-23 03:20 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:25 UTCEPSS rescore
  49. 2026-07-20 17:08 UTCEPSS rescore
  50. 2026-07-19 14:31 UTCEPSS rescore
  51. 2026-07-19 14:31 UTCEPSS rescore
  52. 2026-07-16 17:03 UTCEPSS rescore
  53. 2026-07-16 11:56 UTCVendor advisory
  54. 2026-07-15 16:57 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 12:47 UTCVendor advisory
  57. 2026-07-14 12:43 UTCVendor advisory
  58. 2026-07-13 22:31 UTCEPSS rescore
  59. 2026-07-13 06:13 UTCEPSS rescore
  60. 2026-07-13 06:13 UTCEPSS rescore
  61. 2026-07-12 14:25 UTCVendor advisory
  62. 2026-07-12 05:46 UTCEPSS rescore
  63. 2026-07-11 15:12 UTCVendor advisory
  64. 2026-07-11 08:27 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-10 16:03 UTCVendor advisory
  67. 2026-07-09 19:10 UTCEPSS rescore
  68. 2026-07-09 19:10 UTCEPSS rescore
  69. 2026-07-09 16:53 UTCVendor advisory
  70. 2026-07-08 17:44 UTCVendor advisory
  71. 2026-07-07 18:35 UTCVendor advisory
  72. 2026-07-07 13:46 UTCEPSS rescore
  73. 2026-07-07 13:46 UTCEPSS rescore
  74. 2026-07-06 17:08 UTCVendor advisory
  75. 2026-07-06 02:23 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-54905?
CVE-2026-54905 is a medium vulnerability published on June 19, 2026. concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock after one thread acquires the read lock 32,768 times. The lock stores a thread's local read and write hold counts in one integer. The low 15 bits are used…
When was CVE-2026-54905 disclosed?
CVE-2026-54905 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54905 actively exploited?
CVE-2026-54905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54905?
CVE-2026-54905 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-54905?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54905, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54905

Explore →

Is Your Infrastructure Affected by CVE-2026-54905?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs