CVE-2026-126348: Uffizzi · Addressable display_uri can show misleading hosts with invalid Punycode A-labels
Affects uffizziSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium · fixed in 2.9.1 : update uffizzi when convenient.
Data as of 13 Nov 2026, 21:05 UTC
Thin evidence
One scorer or none| 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: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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewuffizzipkg:brew/uffizziOther threats | 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 returns invalid Punycode labels unchanged in to_unicode, aligning behavior with the native IDNA implementation. Users should upgrade to version 2.9.1 or later. Alternatively, installing libidn and the idn-ruby gem forces Addressable to use the native IDNA implementation, which is not vulnerable. Applications should avoid making security decisions based on display_uri or to_unicode output and instead use normalized_host for hostname comparisons.
Description
A vulnerability in the Addressable Ruby library's pure-Ruby IDNA implementation allows certain invalid Punycode A-labels to be decoded incorrectly by the to_unicode method. This causes display_uri to show misleading hostnames that differ from the actual host used in connections, potentially enabling attackers controlling a domain to impersonate other hosts in displayed URIs. The issue affects Addressable versions 2.0.0 and later when using the pure-Ruby implementation and is fixed in version 2.9.1. The native IDNA implementation is not affected.
References
- github.com/sporkmonger/addressable/security/advisories/GHSA-9crm-g4mf-wc5j (opens in a new tab)
- github.com/sporkmonger/addressable/commit/b8a59cc0e03f8704f1d7c8122fc8f7ef8548362d (opens in a new tab)
- github.com/rubysec/ruby-advisory-db/blob/master/gems/addressable/GHSA-9crm-g4mf-wc5j.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)