OESA-2026-4984: rubygem-addressable security update
Addressable is a replacement for the URI implementation that is part of Ruby's standard library. It more closely conforms to the relevant RFCs and adds support for URI and URL templates. Security Fix(es):
Addressable is an alternative implementation to the URI implementation that is part of Ruby's standard library. From 2.3.0 until 2.9.1, URI template expressions using the explode modifier with the slash, dot, semicolon, question-mark, or ampersand operators generate ambiguous regular expressions. When Template#match or Template#extract processes an attacker-controlled URI beginning with the operator's leading character, optional member separators allow catastrophic backtracking and denial of service on MRI Ruby before 3.2 and JRuby. Addressable 2.9.0 incompletely remediated the earlier template issue because its tests did not reach these operator-prefixed paths. URI parsing and Template#expand are unaffected. This issue is fixed in version 2.9.1.(CVE-2026-126350)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/rubygem-addressableto a version that resolves this vulnerability.Fixed in 2.8.6-4.oe2403sp3 - Upgrade
Upgrade
rubygem/addressableto a version that resolves this vulnerability.Fixed in 2.9.1
Event History
Frequently Asked Questions
Which deployments are exposed to denial of service?
Deployments using Addressable versions 2.3.0 through 2.9.1 are exposed when they call Template#match or Template#extract on attacker-controlled URIs. The denial-of-service condition affects MRI Ruby versions before 3.2 and JRuby.
What input is required to trigger the issue?
An attacker must supply a URI that begins with the leading character of a slash, dot, semicolon, question-mark, or ampersand URI-template operator. The relevant template expression must use that operator with the explode modifier.
Are ordinary URI parsing or template expansion affected?
No. URI parsing and Template#expand are unaffected; the issue is limited to Template#match and Template#extract processing the affected template patterns.
What should be prioritized for remediation?
Update Addressable to version 2.9.1, which fixes the issue. If updating cannot happen immediately, avoid passing untrusted URIs to Template#match or Template#extract for templates using the affected explode-modifier operators.