VulnerabilityPublished 13 Nov 2026

CVE-2026-126348: Krane · Addressable display_uri can show misleading hosts with invalid Punycode A-labels

Affects kraneSource GCVE Database

Compare

Authoritative record:CVE-2026-126348· Medium 4.3

Not known to be exploited · CVSS 4.3 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.3Medium

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.3

Patch: Available – fixed in 2.9.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of confidentiality within 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 returns invalid Punycode labels unchanged in to_unicode. Until upgrading, users can mitigate by installing libidn and the idn-ruby gem to use the native IDNA implementation, which is not vulnerable. Additionally, security decisions should not be based on display_uri or to_unicode output; instead, use normalized_host for host comparisons.

Description

A vulnerability in the pure-Ruby IDNA implementation of the Addressable library allows certain invalid Punycode A-labels to be decoded incorrectly by the to_unicode method. This causes the display_uri method to show misleading hostnames that differ from the actual host used in connections. This discrepancy can lead to confusion or improper trust decisions when comparing displayed hosts against trusted names. The issue affects Addressable versions from 2.0.0 up to but not including 2.9.1 and is fixed in version 2.9.1. Using the native IDNA implementation or avoiding security decisions based on display_uri output mitigates the risk.

Impact

This vulnerability allows an attacker controlling a domain with an invalid Punycode A-label to have the URI display a host name different from the actual host used in connections. This can mislead users or applications that rely on display_uri or to_unicode output for security decisions, potentially causing them to trust a domain they do not control. There is no impact on confidentiality or availability, and the native IDNA implementation is 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