VulnerabilityPublished 13 Nov 2026

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

Affects licenseeSource GCVE Database

Compare

Authoritative record:CVE-2026-126354· Medium 4.8

Not known to be exploited · CVSS 4.8 Medium · fixed in 2.9.1 : update licensee when convenient.

Data as of 13 Nov 2026, 21:18 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.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:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Homebrewlicensee`pkg:brew/licensee`Other threats	Affected >=10.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Addressable to version 2.9.1 or later, where the normalization bug is fixed. If upgrading is not immediately possible, mitigate by rejecting any URIs containing '..' segments, including percent-encoded forms, before performing access control checks. Ensure that the same normalized URI form is used both for allowlist checks and for requests sent to other components to avoid discrepancies.

Description

Addressable versions 2.2.5 through 2.9.0 contain a URI normalization flaw where paths with multiple '..' segments are incorrectly resolved, deviating from RFC 3986. This can cause normalized paths to appear within an allowed directory while the original path actually points outside it, potentially enabling path traversal bypasses of allowlist checks. The issue is fixed in version 2.9.1. Applications that use Addressable's normalized path for access control but send the original URI to other components that resolve paths correctly are vulnerable. Rejecting paths with '..' segments or upgrading to 2.9.1 mitigates the issue.

Impact

This vulnerability can lead to path traversal bypasses in applications that rely on Addressable's normalization for access control decisions but forward the original URI to other components that resolve paths differently. An attacker can craft URIs that pass allowlist checks but access unauthorized paths, potentially exposing sensitive resources. The impact depends on the application's use of Addressable normalization and whether it sends unnormalized URIs to other systems. Applications using Addressable normalization consistently or rejecting '..' segments are not affected.

Summary

The Addressable Ruby library's URI.normalize_path method incorrectly resolves dotted path segments when multiple '..' segments appear before any other are resolved. Specifically, it replaces all occurrences of '/../..' in one step, causing paths like '/../../public/x/../../secret' to normalize to '/public/x/secret' instead of the RFC 3986 compliant '/secret'. This discrepancy can lead to security issues where an application uses Addressable's normalized path for allowlist checks but sends the original URI to components that resolve paths according to RFC 3986, allowing attackers to bypass path-based access controls. The flaw was introduced in version 2.2.5 and fixed in 2.9.1 by replacing the rewrite loop with a single pass that correctly follows RFC 3986 §5.2.4.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 21:18 UTC

Technical details

References

Community reviews

Related threats