<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 20:51:07 +0000</lastBuildDate>
    <item>
      <title>BREW-krane-CVE-2026-126349 — Addressable display_uri can show misleading hosts containing bidi and invisible characters</title>
      <link>https://cve.radiocsirt.org/vuln/brew-krane-cve-2026-126349</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: krane&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;- In the pure-Ruby IDNA implementation, all such characters are decoded, including those that IDNA&amp;#39;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;The pure-Ruby IDNA implementation is affected in Addressable &amp;gt;= 2.0.0. The native IDNA implementation is affected in Addressable &amp;gt;= 2.5.2, when `to_unicode` began accepting characte…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: krane&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;- In the pure-Ruby IDNA implementation, all such characters are decoded, including those that IDNA&amp;#39;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;The pure-Ruby IDNA implementation is affected in Addressable &amp;gt;= 2.0.0. The native IDNA implementation is affected in Addressable &amp;gt;= 2.5.2, when `to_unicode` began accepting characte…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-krane-cve-2026-126349</guid>
    </item>
    <item>
      <title>EUVD-2026-405789</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405789</link>
      <description>EUVD-2026-405789</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405789</guid>
    </item>
    <item>
      <title>fkie_cve-2026-126349</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126349</link>
      <description>&lt;p&gt;Addressable is an alternative implementation to the URI implementation that is part of Ruby&amp;#39;s standard library. From 2.0.0 until 2.9.1, Addressable::IDNA.to_unicode can decode Punycode labels that contain bidirectional controls, zero-width characters, control characters, or other default-ignorable format characters. Addressable::URI#display_uri can consequently show a reordered or visually indistinguishable hostname even though host, normalized_host, and network connections use the original encoded hostname. The pure-Ruby backend accepts the full prohibited set, while the native libidn backend is affected from 2.5.2 for characters added after Unicode 3.2. This issue is fixed in version 2.9.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Addressable is an alternative implementation to the URI implementation that is part of Ruby&amp;#39;s standard library. From 2.0.0 until 2.9.1, Addressable::IDNA.to_unicode can decode Punycode labels that contain bidirectional controls, zero-width characters, control characters, or other default-ignorable format characters. Addressable::URI#display_uri can consequently show a reordered or visually indistinguishable hostname even though host, normalized_host, and network connections use the original encoded hostname. The pure-Ruby backend accepts the full prohibited set, while the native libidn backend is affected from 2.5.2 for characters added after Unicode 3.2. This issue is fixed in version 2.9.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-126349</guid>
    </item>
    <item>
      <title>GHSA-539f-xcgw-2gjg — Addressable display_uri can show misleading hosts containing bidi and invisible characters</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-539f-xcgw-2gjg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: addressable&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;- In the pure-Ruby IDNA implementation, all such characters are decoded, including those that IDNA&amp;#39;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;The pure-Ruby IDNA implementation is affected in Addressable &amp;gt;= 2.0.0. The native IDNA implementation is affected in Addressable &amp;gt;= 2.5.2, when `to_unicode` began accepting characte…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: addressable&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;- In the pure-Ruby IDNA implementation, all such characters are decoded, including those that IDNA&amp;#39;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;The pure-Ruby IDNA implementation is affected in Addressable &amp;gt;= 2.0.0. The native IDNA implementation is affected in Addressable &amp;gt;= 2.5.2, when `to_unicode` began accepting characte…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-539f-xcgw-2gjg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-126349 — Addressable display_uri can show misleading hosts containing bidi and invisible characters</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-126349</link>
      <description>msrc_CVE-2026-126349</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-126349</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-126349</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126349</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: ruby-addressable, Ubuntu:Pro:18.04:LTS: ruby-addressable, Ubuntu:Pro:20.04:LTS: ruby-addressable, Ubuntu:Pro:22.04:LTS: ruby-addressable, Ubuntu:Pro:24.04:LTS: ruby-addressable, Ubuntu:26.10: ruby-addressable, Ubuntu:Pro:26.04:LTS: ruby-addressable&lt;/p&gt;
&lt;p&gt;Addressable is an alternative implementation to the URI implementation that is part of Ruby&amp;#39;s standard library. From 2.0.0 until 2.9.1, Addressable::IDNA.to_unicode can decode Punycode labels that contain bidirectional controls, zero-width characters, control characters, or other default-ignorable format characters. Addressable::URI#display_uri can consequently show a reordered or visually indistinguishable hostname even though host, normalized_host, and network connections use the original encoded hostname. The pure-Ruby backend accepts the full prohibited set, while the native libidn backend is affected from 2.5.2 for characters added after Unicode 3.2. This issue is fixed in version 2.9.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: ruby-addressable, Ubuntu:Pro:18.04:LTS: ruby-addressable, Ubuntu:Pro:20.04:LTS: ruby-addressable, Ubuntu:Pro:22.04:LTS: ruby-addressable, Ubuntu:Pro:24.04:LTS: ruby-addressable, Ubuntu:26.10: ruby-addressable, Ubuntu:Pro:26.04:LTS: ruby-addressable&lt;/p&gt;
&lt;p&gt;Addressable is an alternative implementation to the URI implementation that is part of Ruby&amp;#39;s standard library. From 2.0.0 until 2.9.1, Addressable::IDNA.to_unicode can decode Punycode labels that contain bidirectional controls, zero-width characters, control characters, or other default-ignorable format characters. Addressable::URI#display_uri can consequently show a reordered or visually indistinguishable hostname even though host, normalized_host, and network connections use the original encoded hostname. The pure-Ruby backend accepts the full prohibited set, while the native libidn backend is affected from 2.5.2 for characters added after Unicode 3.2. This issue is fixed in version 2.9.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126349</guid>
    </item>
  </channel>
</rss>
