<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T18:45:51.752961+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-krane-cve-2026-126348</id>
    <title>BREW-krane-CVE-2026-126348 — Addressable display_uri can show misleading hosts with invalid Punycode A-labels</title>
    <updated>2026-11-16T18:45:51.758466+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: krane</p>
<p>### Impact</p>
<p>`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:</p>
<p>- labels that decode to only ASCII characters, e.g. `xn--google-` decodes to `google`;
- 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.</p>
<p>`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.</p>
<p>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.</p>
<p>### Affected Versions</p>
<p>This vulnerability affects Addressable &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.</p>
<p>### Workarounds</p>
<p>- Install libidn and the `idn-ruby` gem, so that Addressable uses the native IDNA implementation.
- Don't make security d…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-krane-cve-2026-126348"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-405788</id>
    <title>EUVD-2026-405788</title>
    <updated>2026-11-16T18:45:51.758534+00:00</updated>
    <content>EUVD-2026-405788</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-405788"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126348</id>
    <title>fkie_cve-2026-126348</title>
    <updated>2026-11-16T18:45:51.758550+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Addressable is an alternative implementation to the URI implementation that is part of Ruby'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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-126348"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9crm-g4mf-wc5j</id>
    <title>GHSA-9crm-g4mf-wc5j — Addressable display_uri can show misleading hosts with invalid Punycode A-labels</title>
    <updated>2026-11-16T18:45:51.758577+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> RubyGems: addressable</p>
<p>### Impact</p>
<p>`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:</p>
<p>- labels that decode to only ASCII characters, e.g. `xn--google-` decodes to `google`;
- 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.</p>
<p>`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.</p>
<p>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.</p>
<p>### Affected Versions</p>
<p>This vulnerability affects Addressable &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.</p>
<p>### Workarounds</p>
<p>- Install libidn and the `idn-ruby` gem, so that Addressable uses the native IDNA implementation.
- Don't make security d…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9crm-g4mf-wc5j"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-126348</id>
    <title>msrc_CVE-2026-126348 — Addressable display_uri can show misleading hosts with invalid Punycode A-labels</title>
    <updated>2026-11-16T18:45:51.758617+00:00</updated>
    <content>msrc_CVE-2026-126348</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-126348"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126348</id>
    <title>UBUNTU-CVE-2026-126348</title>
    <updated>2026-11-16T18:45:51.758633+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>Addressable is an alternative implementation to the URI implementation that is part of Ruby'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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126348"/>
  </entry>
</feed>
