rubyconcurrency records
3 published records for vendor rubyconcurrency.
Researcher profile
- Entered KEV
- 0 · 0%
- Weaponized
- 0 · 0%
- Pre-auth RCE
- 0
- With a fix record
- 100%
- Median publish → KEV
- No record has entered KEV
Recurring classes
- CWE-128 Wrap-around Error1
- CWE-414 Missing Lock Check1
- CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')1
The weakness classes this vendor ships most often: where to look.
CWEAttack profile
All records
3 records| Action | CVE | Vulnerability | Severity | KEV | EPSS | Published |
|---|---|---|---|---|---|---|
32Monitor | CVE-2026-54904No exploit | concurrent-ruby: `AtomicReference#update` livelocks when the stored value is `Float::NAN`rubyconcurrency · concurrent ruby · CWE-835 | High8.2 | — | 0.7% | Jun 24, 2026 |
8Monitor | CVE-2026-54906No exploit | concurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruptionrubyconcurrency · concurrent ruby · CWE-414 | Low2.1 | — | 0.3% | Jun 24, 2026 |
8Monitor | CVE-2026-54905No exploit | concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivityrubyconcurrency · concurrent ruby · CWE-128 | Low2.0 | — | 0.2% | Jun 24, 2026 |
- CVE-2026-5490432Monitor
concurrent-ruby: `AtomicReference#update` livelocks when the stored value is `Float::NAN`
HighCVSS 8.2No exploitEPSS 1%rubyconcurrency · concurrent rubyJun 24, 2026
- CVE-2026-549068Monitor
concurrent-ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption
LowCVSS 2.1No exploitEPSS 0%rubyconcurrency · concurrent rubyJun 24, 2026
- CVE-2026-549058Monitor
concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
LowCVSS 2.0No exploitEPSS 0%rubyconcurrency · concurrent rubyJun 24, 2026