ManageIQ / ManageIQ/foreman_api_client

CVE-2026-54906 (Medium) detected in concurrent-ruby-1.3.5.gem

Open
#69 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Mend: dependency security vulnerability
Dominant language
Ruby
Stars
2
Forks
12
PR merge metrics
No merged PRs in 30d

Description

## CVE-2026-54906 - Medium Severity Vulnerability
Vulnerable Library - concurrent-ruby-1.3.5.gem

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


Library home page: https://rubygems.org/gems/concurrent-ruby-1.3.5.gem


Path to dependency file: /Gemfile.lock


Path to vulnerable library: /vendor/cache/concurrent-ruby-1.3.5.gem


Dependency Hierarchy:
- manageiq-style-1.5.8.gem (Root Library)
- rubocop-rails-2.29.1.gem
- activesupport-8.0.3.gem
- :x: **concurrent-ruby-1.3.5.gem** (Vulnerable Library)

Found in base branch: master



Vulnerability Details



concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReadWriteLock#release_write_lock does not verify that the calling thread acquired the write lock. Any thread with access to the lock object can release an active write lock held by another thread. A second writer can then enter its critical section while the first writer is still running. Concurrent::ReadWriteLock#release_read_lock also decrements the shared counter even when no read lock is held. Calling it on a fresh lock changes the counter from 0 to -1, after which normal read acquisition raises Concurrent::ResourceLimitError. This is a synchronization correctness issue in the public Concurrent::ReadWriteLock API. This vulnerability is fixed in 1.3.7.

Publish Date: 2026-06-24

URL: CVE-2026-54906



CVSS 3 Score Details (4.0)

Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: Low


For more information on CVSS3 Scores, click here.


Suggested Fix

Type: Upgrade version


Release Date: 2026-06-19


Fix Resolution: https://github.com/ruby-concurrency/concurrent-ruby.git - v1.3.7

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with /Gemfile.lock and /vendor/cache/concurrent-ruby-1.3.5.gem, following the dependency path from manageiq-style through rubocop-rails and activesupport. Update the vulnerable dependency to concurrent-ruby 1.3.7 and verify that the dependency scan no longer reports CVE-2026-54906.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.