<?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://db.gcve.eu</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>Sun, 25 Oct 2026 22:49:46 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-105483</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-105483</link>
      <description>&lt;p&gt;A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).&lt;/p&gt;
&lt;p&gt;`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x** and **24.x**.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).&lt;/p&gt;
&lt;p&gt;`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x** and **24.x**.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-105483</guid>
    </item>
    <item>
      <title>GHSA-8h4p-qpcq-gq24</title>
      <link>https://db.gcve.eu/vuln/ghsa-8h4p-qpcq-gq24</link>
      <description>&lt;p&gt;A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).&lt;/p&gt;
&lt;p&gt;`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x** and **24.x**.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).&lt;/p&gt;
&lt;p&gt;`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.&lt;/p&gt;
&lt;p&gt;This vulnerability affects Node.js **26.x** and **24.x**.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8h4p-qpcq-gq24</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-105483 — A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a co…</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-105483</link>
      <description>msrc_CVE-2026-105483</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-105483</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:12248-1 — corepack24-24.22.1-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2026:12248-1</link>
      <description>&lt;p&gt;corepack24-24.22.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;corepack24-24.22.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2026:12248-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-105483</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-105483</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: nodejs, Ubuntu:Pro:16.04:LTS: nodejs, Ubuntu:Pro:18.04:LTS: nodejs, Ubuntu:Pro:20.04:LTS: nodejs, Ubuntu:Pro:22.04:LTS: nodejs, Ubuntu:24.04:LTS: nodejs, Ubuntu:26.10: nodejs, Ubuntu:26.04:LTS: nodejs&lt;/p&gt;
&lt;p&gt;[Unknown description]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: nodejs, Ubuntu:Pro:16.04:LTS: nodejs, Ubuntu:Pro:18.04:LTS: nodejs, Ubuntu:Pro:20.04:LTS: nodejs, Ubuntu:Pro:22.04:LTS: nodejs, Ubuntu:24.04:LTS: nodejs, Ubuntu:26.10: nodejs, Ubuntu:26.04:LTS: nodejs&lt;/p&gt;
&lt;p&gt;[Unknown description]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-105483</guid>
    </item>
  </channel>
</rss>
