LowGHSA-539f-xcgw-2gjgCVE-2026-126349

Addressable display_uri can show misleading hosts containing bidi and invisible characters

Published 12 Nov 2026 · Updated 12 Nov 2026

Is your project on an affected addressable?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

addressableRubyGems
Affected
>=2.0.0 <2.9.1
Fixed in
2.9.1
Update to the fixed version for your release line, for example:bundle update --conservative addressable # Gemfile: '>= 2.9.1'

Details

Impact

Addressable::IDNA.to_unicode decodes Punycode labels (labels beginning with xn--) that contain characters which change how text is displayed without being visible themselves. These include bidirectional controls such as U+202E RIGHT-TO-LEFT OVERRIDE and U+2066–U+2069, zero-width characters, and other invisible format characters. Addressable::URI#display_uri uses to_unicode, so it can display a host whose characters appear reordered or which looks identical to a different host. For example, the host of http://xn--abcmoc-dm0c.com/ is displayed as abc, U+202E, moc.com, and the override makes everything after abc render right to left.

Parsing, host, normalized_host and any connection made from the URI are not affected. Only the displayed form is. Applications that show display_uri to users (link previews, chat and email clients, admin interfaces) can be used to make a malicious domain look like a trusted one.

  • In the pure-Ruby IDNA implementation, all such characters are decoded, including those that IDNA's nameprep profile prohibits.
  • In the native IDNA implementation, used when libidn and the idn-ruby gem are installed, libidn rejects most of them, but not characters added to Unicode after version 3.2, such as U+061C and U+2066–U+2069.

Affected Versions

The pure-Ruby IDNA implementation is affected in Addressable >= 2.0.0. The native IDNA implementation is affected in Addressable >= 2.5.2, when to_unicode began accepting characters unassigned in Unicode 3.2. It is fixed in 2.9.1 for both implementations, where such labels are returned unchanged.

Workarounds

  • Install libidn and the idn-ruby gem, so that Addressable uses the native IDNA implementation. This reduces the affected characters to those added since Unicode 3.2.
  • Check displayed hosts for bidirectional and invisible characters (e.g., /[\p{Cc}\p{Cf}\p{Default_Ignorable_Code_Point}]/) and fall back to normalized_host when one is present.

Credits

Reported by @andrewstellman.

For more information

If there are any questions or comments about this advisory:

Is GHSA-539f-xcgw-2gjg 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

  • MediumCVE-2026-126348Addressable display_uri can show misleading hosts with invalid Punycode A-labels · 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
All 8 advisories for addressable

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.