VulnerabilityPublished 13 Nov 2026

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

Affects kraneSource 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 krane when convenient.

Data as of 13 Nov 2026, 21:17 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
Homebrewkrane`pkg:brew/krane`Other threats	Affected >=3.7.4	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 URI normalization per RFC 3986. Applications should upgrade to this version to resolve the issue. As a workaround for unpatched versions, applications should either reject any paths containing '..' segments (including percent-encoded forms) before making access decisions or ensure that the same normalized URI value is used consistently for both allowlist checks and the actual request handling. This prevents discrepancies between normalization methods from being exploited.

Description

Addressable URI normalization in krane versions starting from 2.2.5 up to 2.9.0 incorrectly resolves some paths containing '..' segments, deviating from RFC 3986. This causes paths that should be normalized above the root to be incorrectly resolved, potentially allowing path traversal past allowlist checks. The issue is fixed in version 2.9.1 by aligning normalization with RFC 3986. Applications that use Addressable's normalization for access control but send the original URI to other resolvers may be vulnerable. Workarounds include rejecting paths with '..' segments or using consistent normalization for checks and requests.

Impact

The vulnerability can lead to path traversal bypassing allowlist checks in applications that rely on Addressable's normalization for access decisions but send the original URI to other components that resolve paths according to RFC 3986. This discrepancy can allow attackers to access unauthorized paths outside the intended allowlist. The impact is application-dependent and limited to scenarios where the normalization mismatch is exploited. There is no indication of remote code execution or denial of service. The CVSS score is 4.8 (medium), reflecting limited confidentiality and integrity impact without availability impact.

Summary

The vulnerability in Addressable's URI normalization (introduced in version 2.2.5 and present through 2.9.0) arises from the method normalize_path incorrectly handling dotted path segments ('..'). Specifically, when the path attempts to climb above the root directory, the normalization replaces all occurrences of '/../..' with '/', including those that should remove preceding segments, resulting in incorrect path resolution. This behavior diverges from RFC 3986 §5.2.4, which properly drops leading '..' segments that cannot go above root and correctly resolves subsequent segments. The flaw affects methods such as URI#normalize, URI#join, URI#==, and URI#===. An attacker can exploit this discrepancy if an application uses Addressable's normalized path for allowlist checks but forwards the original URI to components that resolve paths per RFC 3986, potentially bypassing access controls. The issue is fixed in Addressable version 2.9.1 by replacing the rewrite loop with a single pass that correctly follows RFC 3986. Versions 2.0.0 through 2.2.4 and earlier are not affected.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats