Addressable display_uri can show misleading hosts with invalid Punycode A-labels
Published 12 Nov 2026 · Updated 12 Nov 2026
Is your project on an affected addressable?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.0.0 <2.9.1
- Fixed in
- 2.9.1
bundle update --conservative addressable # Gemfile: '>= 2.9.1'Details
Impact
Addressable::IDNA.to_unicode, in the pure-Ruby IDNA implementation, decodes Punycode labels (labels beginning with xn--) that are not valid A-labels. Those labels are returned in decoded form, when they should be returned unchanged. That includes:
- labels that decode to only ASCII characters, e.g.
xn--google-decodes togoogle; - labels that decode to text that doesn't convert back to the same label (RFC 3490 §4.2), e.g. text that isn't in normalized form.
Addressable::URI#display_uri uses to_unicode, so for https://xn--google-.example.org/ it displays the host google.example.org, while #host, #normalized_host and any connection made from the URI use xn--google-.example.org. An attacker who controls a domain can therefore have a URI displayed as a host they don't control. Applications that compare the result of to_unicode against a list of trusted names can likewise treat two different hosts as the same.
The native IDNA implementation, used when libidn and the idn-ruby gem are installed, is not affected. to_ascii and normalized_host are not affected.
Affected Versions
This vulnerability affects Addressable >= 2.0.0, the first version with the pure-Ruby IDNA implementation, when that implementation is in use. It is fixed in 2.9.1, where such labels are returned unchanged, as with libidn.
Workarounds
- Install libidn and the
idn-rubygem, so that Addressable uses the native IDNA implementation. - Don't make security decisions on
display_uriorto_unicodeoutput. Compare hosts usingnormalized_host.
Credits
Reported by @tonghuaroot.
For more information
If there are any questions or comments about this advisory:
Is GHSA-9crm-g4mf-wc5j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected addressable, and gives you the command that fixes it.
More advisories for addressable
- LowCVE-2026-126349Addressable display_uri can show misleading hosts containing bidi and invisible characters · 12 Nov 2026
- MediumCVE-2026-126351Addressable: Denial of service in URI path normalization · 12 Nov 2026
- MediumCVE-2026-126350Addressable: Regular Expression Denial of Service in templates with certain exploded expressions · 12 Nov 2026
- MediumCVE-2026-126352Addressable: Regular Expression Denial of Service in templates with multiple variables · 12 Nov 2026
- MediumCVE-2026-126354Addressable URI normalization resolves some dotted path segments to the wrong path · 12 Nov 2026
- HighCVE-2026-35611Addressable has a Regular Expression Denial of Service in Addressable templates · 8 Apr 2026
References
- Linkgithub.com/sporkmonger/addressable/security/advisories/GHSA-9crm-g4mf-wc5j
- Linkgithub.com/sporkmonger/addressable/commit/b8a59cc0e03f8704f1d7c8122fc8f7ef8548362d
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/addressable/GHSA-9crm-g4mf-wc5j.yml
- Packagegithub.com/sporkmonger/addressable
- Linkgithub.com/sporkmonger/addressable/releases/tag/addressable-2.9.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.