<?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 18:37:40 +0000</lastBuildDate>
    <item>
      <title>BREW-krane-CVE-2026-126348 — Addressable display_uri can show misleading hosts with invalid Punycode A-labels</title>
      <link>https://cve.radiocsirt.org/vuln/brew-krane-cve-2026-126348</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`, 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:&lt;/p&gt;
&lt;p&gt;- labels that decode to only ASCII characters, e.g. `xn--google-` decodes to `google`;
- labels that decode to text that doesn&amp;#39;t convert back to the same label (RFC 3490 §4.2), e.g. text that isn&amp;#39;t in normalized form.&lt;/p&gt;
&lt;p&gt;`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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;This vulnerability affects Addressable &amp;gt;= 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.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;- Install libidn and the `idn-ruby` gem, so that Addressable uses the native IDNA implementation.
- Don&amp;#39;t make security d…&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`, 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:&lt;/p&gt;
&lt;p&gt;- labels that decode to only ASCII characters, e.g. `xn--google-` decodes to `google`;
- labels that decode to text that doesn&amp;#39;t convert back to the same label (RFC 3490 §4.2), e.g. text that isn&amp;#39;t in normalized form.&lt;/p&gt;
&lt;p&gt;`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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;This vulnerability affects Addressable &amp;gt;= 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.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;- Install libidn and the `idn-ruby` gem, so that Addressable uses the native IDNA implementation.
- Don&amp;#39;t make security d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-krane-cve-2026-126348</guid>
    </item>
    <item>
      <title>EUVD-2026-405788</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405788</link>
      <description>EUVD-2026-405788</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405788</guid>
    </item>
    <item>
      <title>fkie_cve-2026-126348</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126348</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, the pure-Ruby Addressable::IDNA.to_unicode implementation decodes invalid Punycode A-labels instead of returning them unchanged. Labels that decode to ASCII text or fail to convert back to the same A-label can therefore make Addressable::URI#display_uri show a trusted-looking host while host, normalized_host, and the connection target retain the attacker-controlled encoded host. A trusted-name comparison using Addressable::IDNA.to_unicode output can also treat two different hosts as the same without displaying the URI. The native libidn implementation, to_ascii, and normalized_host are unaffected. 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, the pure-Ruby Addressable::IDNA.to_unicode implementation decodes invalid Punycode A-labels instead of returning them unchanged. Labels that decode to ASCII text or fail to convert back to the same A-label can therefore make Addressable::URI#display_uri show a trusted-looking host while host, normalized_host, and the connection target retain the attacker-controlled encoded host. A trusted-name comparison using Addressable::IDNA.to_unicode output can also treat two different hosts as the same without displaying the URI. The native libidn implementation, to_ascii, and normalized_host are unaffected. 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-126348</guid>
    </item>
    <item>
      <title>GHSA-9crm-g4mf-wc5j — Addressable display_uri can show misleading hosts with invalid Punycode A-labels</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9crm-g4mf-wc5j</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`, 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:&lt;/p&gt;
&lt;p&gt;- labels that decode to only ASCII characters, e.g. `xn--google-` decodes to `google`;
- labels that decode to text that doesn&amp;#39;t convert back to the same label (RFC 3490 §4.2), e.g. text that isn&amp;#39;t in normalized form.&lt;/p&gt;
&lt;p&gt;`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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;This vulnerability affects Addressable &amp;gt;= 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.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;- Install libidn and the `idn-ruby` gem, so that Addressable uses the native IDNA implementation.
- Don&amp;#39;t make security d…&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`, 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:&lt;/p&gt;
&lt;p&gt;- labels that decode to only ASCII characters, e.g. `xn--google-` decodes to `google`;
- labels that decode to text that doesn&amp;#39;t convert back to the same label (RFC 3490 §4.2), e.g. text that isn&amp;#39;t in normalized form.&lt;/p&gt;
&lt;p&gt;`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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;This vulnerability affects Addressable &amp;gt;= 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.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;- Install libidn and the `idn-ruby` gem, so that Addressable uses the native IDNA implementation.
- Don&amp;#39;t make security d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9crm-g4mf-wc5j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-126348 — Addressable display_uri can show misleading hosts with invalid Punycode A-labels</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-126348</link>
      <description>msrc_CVE-2026-126348</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-126348</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-126348</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126348</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, the pure-Ruby Addressable::IDNA.to_unicode implementation decodes invalid Punycode A-labels instead of returning them unchanged. Labels that decode to ASCII text or fail to convert back to the same A-label can therefore make Addressable::URI#display_uri show a trusted-looking host while host, normalized_host, and the connection target retain the attacker-controlled encoded host. A trusted-name comparison using Addressable::IDNA.to_unicode output can also treat two different hosts as the same without displaying the URI. The native libidn implementation, to_ascii, and normalized_host are unaffected. 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, the pure-Ruby Addressable::IDNA.to_unicode implementation decodes invalid Punycode A-labels instead of returning them unchanged. Labels that decode to ASCII text or fail to convert back to the same A-label can therefore make Addressable::URI#display_uri show a trusted-looking host while host, normalized_host, and the connection target retain the attacker-controlled encoded host. A trusted-name comparison using Addressable::IDNA.to_unicode output can also treat two different hosts as the same without displaying the URI. The native libidn implementation, to_ascii, and normalized_host are unaffected. 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-126348</guid>
    </item>
  </channel>
</rss>
