Skip to main content
VulnerabilityPublished

CVE-2026-126354: Addressable URI normalization resolves some dotted path segments to the wrong path

Affects addressableSource GCVE Database

0
Compare
Authoritative record:CVE-2026-126354· Medium 4.8

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

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
RubyGemsaddressableAffected
  • >=2.2.5 <2.9.1
Fixed in
  • 2.9.1

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

Community reviews

Loading reviews…