<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T15:54:27.111629+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/brew-carton-cve-2026-19953</id>
    <title>BREW-carton-CVE-2026-19953 — URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization i…</title>
    <updated>2026-10-01T15:54:27.183931+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: carton</p>
<p>URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep.</p>
<p>nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label.</p>
<p>Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/brew-carton-cve-2026-19953"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-19953</id>
    <title>fkie_cve-2026-19953</title>
    <updated>2026-10-01T15:54:27.184030+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep.</p>
<p>nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label.</p>
<p>Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-19953"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-wf9v-63v3-ff2x</id>
    <title>GHSA-wf9v-63v3-ff2x</title>
    <updated>2026-10-01T15:54:27.184070+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep.</p>
<p>nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label.</p>
<p>Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-wf9v-63v3-ff2x"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-19953</id>
    <title>msrc_CVE-2026-19953 — URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization i…</title>
    <updated>2026-10-01T15:54:27.184094+00:00</updated>
    <content>msrc_CVE-2026-19953</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-19953"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/oesa-2026-3588</id>
    <title>OESA-2026-3588 — perl-URI security update</title>
    <updated>2026-10-01T15:54:27.184437+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: perl-URI</p>
<p>This module implements the URI class. Objects of this class represent &amp;amp;quot;Uniform Resource Identifier references&amp;amp;quot; as specified in RFC 2396 (and updated by RFC 2732).

Security Fix(es):</p>
<p>URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep. nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label. Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.(CVE-2026-19953)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/oesa-2026-3588"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/opensuse-su-2026:11663-1</id>
    <title>openSUSE-SU-2026:11663-1 — perl-URI-5.360.0-1.1 on GA media</title>
    <updated>2026-10-01T15:54:27.184634+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>perl-URI-5.360.0-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/opensuse-su-2026:11663-1"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/suse-su-2026:23633-1</id>
    <title>SUSE-SU-2026:23633-1 — Security update for perl-URI</title>
    <updated>2026-10-01T15:54:27.184718+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for perl-URI</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/suse-su-2026:23633-1"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-19953</id>
    <title>UBUNTU-CVE-2026-19953</title>
    <updated>2026-10-01T15:54:27.184782+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:14.04:LTS: liburi-perl, Ubuntu:16.04:LTS: liburi-perl, Ubuntu:18.04:LTS: liburi-perl, Ubuntu:20.04:LTS: liburi-perl, Ubuntu:22.04:LTS: liburi-perl, Ubuntu:24.04:LTS: liburi-perl, Ubuntu:26.04:LTS: liburi-perl</p>
<p>URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep. nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label. Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-19953"/>
  </entry>
</feed>
