CVE-2026-126350: rubygem-addressable security update
Affects rubygem-addressableSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.8.6-4.oe2403sp4 when convenient.
Data as of 19 Nov 2026, 02:56 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 2.8.6-4.oe2403sp4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade rubygem-addressable to 2.8.6-4.oe2403sp4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP4rubygem-addressablepkg:rpm/openEuler/rubygem-addressable&distro=openEuler-24.03-LTS-SP4Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in rubygem-addressable version 2.8.6-4.oe2403sp4 and later. Users should upgrade to this fixed version or later to remediate the vulnerability. No other mitigation actions are indicated by the vendor advisory.
Description
The rubygem-addressable library, used as an alternative URI implementation in Ruby, contains a vulnerability in versions prior to 2.8.6-4.oe2403sp4. From version 2.3.0 until 2.9.1, certain URI template expressions with the explode modifier and specific operators generate ambiguous regular expressions that can cause catastrophic backtracking. This leads to denial of service (DoS) on MRI Ruby versions before 3.2 and JRuby. The issue was incompletely fixed in version 2.9.0 and fully resolved in version 2.9.1.