CVE-2026-126354: Addressable URI normalization resolves some dotted path segments to the wrong path
Affects addressableSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.9.1 when convenient.
Data as of 12 Nov 2026, 23:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.8 |
|---|
- Patch
- Available – fixed in 2.9.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation 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 12 Nov 2026.
What to do
Upgrade addressable to 2.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RubyGemsaddressable | 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 fix is available in Addressable version 2.9.1, which correctly implements RFC 3986 path normalization. Applications should upgrade to version 2.9.1 or later. As a workaround for unpatched versions, applications should reject any paths containing '..' segments, including percent-encoded forms, before making access decisions or ensure that the same normalized path value is used for both allowlist checks and requests.
Description
Addressable versions from 2.2.5 up to but not including 2.9.1 contain a URI normalization flaw where paths with multiple '..' segments are incorrectly resolved. This causes some paths to normalize differently than specified by RFC 3986, potentially allowing path traversal bypasses of allowlist checks. The issue is fixed in version 2.9.1.
References
- github.com/sporkmonger/addressable/security/advisories/GHSA-8gmh-2hhj-2hv9 (opens in a new tab)
- github.com/sporkmonger/addressable/commit/25c7c412a2f7e06c3cac92872e831f6d053703c5 (opens in a new tab)
- github.com/rubysec/ruby-advisory-db/blob/master/gems/addressable/GHSA-8gmh-2hhj-2hv9.yml (opens in a new tab)
- github.com/sporkmonger/addressable (opens in a new tab)
- github.com/sporkmonger/addressable/releases/tag/addressable-2.9.1 (opens in a new tab)