<?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 17:26:29 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:96088 — Important: nodejs24 security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:96088</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: nodejs24, AlmaLinux:10: nodejs24-devel, AlmaLinux:10: nodejs24-docs, AlmaLinux:10: nodejs24-full-i18n, AlmaLinux:10: nodejs24-libs, AlmaLinux:10: nodejs24-npm&lt;/p&gt;
&lt;p&gt;Node.js is a platform built on Chrome&amp;#39;s JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)
  * brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)
  * undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)
  * undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)
  * undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)
  * undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)
  * nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames (CVE-2026-105483)
  * nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)
  * nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:RHEL-295759)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: nodejs24, AlmaLinux:10: nodejs24-devel, AlmaLinux:10: nodejs24-docs, AlmaLinux:10: nodejs24-full-i18n, AlmaLinux:10: nodejs24-libs, AlmaLinux:10: nodejs24-npm&lt;/p&gt;
&lt;p&gt;Node.js is a platform built on Chrome&amp;#39;s JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)
  * brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)
  * undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)
  * undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)
  * undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)
  * undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)
  * nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames (CVE-2026-105483)
  * nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)
  * nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:RHEL-295759)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:96088</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1539 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1539</link>
      <description>certfr-2026-avi-1539</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1539</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-OM39297 — undici is an HTTP client library for Node</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-om39297</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: npm&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the npm package. undici is an HTTP client library for Node.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: npm&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the npm package. undici is an HTTP client library for Node.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-om39297</guid>
    </item>
    <item>
      <title>EUVD-2026-388463</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-388463</link>
      <description>EUVD-2026-388463</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-388463</guid>
    </item>
    <item>
      <title>fkie_cve-2026-87018</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-87018</link>
      <description>&lt;p&gt;undici is an HTTP client library for Node.js. In versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, the client process crashes when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with a certificate-altname error, but undici&amp;#39;s established-socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught assertion that terminates the Node.js process, affecting both the HTTP/1.1 and HTTP/2 paths. A malicious or compromised HTTPS endpoint reached through undici or the global fetch() can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process, and exploitation needs no CA compromise because the attacker controls the endpoint and can present two ordinary valid certificates. Only TLS 1.2 is affected, since TLS 1.3 does not support renegotiation. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. As a workaround, restrict outbound connections to TLS 1.3 so renegotiation cannot occur, when the target endpoints support it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;undici is an HTTP client library for Node.js. In versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, the client process crashes when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with a certificate-altname error, but undici&amp;#39;s established-socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught assertion that terminates the Node.js process, affecting both the HTTP/1.1 and HTTP/2 paths. A malicious or compromised HTTPS endpoint reached through undici or the global fetch() can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process, and exploitation needs no CA compromise because the attacker controls the endpoint and can present two ordinary valid certificates. Only TLS 1.2 is affected, since TLS 1.3 does not support renegotiation. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. As a workaround, restrict outbound connections to TLS 1.3 so renegotiation cannot occur, when the target endpoints support it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-87018</guid>
    </item>
    <item>
      <title>GHSA-qrxm-fqhp-jwvm — undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qrxm-fqhp-jwvm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: undici&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;undici crashes the client process when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with `ERR_TLS_CERT_ALTNAME_INVALID`. undici&amp;#39;s established socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught `AssertionError` that terminates the Node.js process. Both the HTTP/1.1 and HTTP/2 paths are affected.&lt;/p&gt;
&lt;p&gt;A malicious or compromised HTTPS endpoint reached through undici or the global `fetch()` can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process. Only TLS 1.2 is affected, because TLS 1.3 does not support renegotiation. Exploitation does not require a CA compromise: the attacker controls the endpoint and can present two ordinary valid certificates, the first matching the requested URL and the second intentionally not matching it.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Upgrade to undici 6.29.1, 7.30.1, or 8.12.2.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Restrict outbound connections to TLS 1.3, for example by setting `connect: { minVersion: &amp;#39;TLSv1.3&amp;#39;, maxVersion: &amp;#39;TLSv1.3&amp;#39; }` on the client or agent, so that renegotiation cannot occur, when the target endpoints support TLS 1.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: undici&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;undici crashes the client process when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with `ERR_TLS_CERT_ALTNAME_INVALID`. undici&amp;#39;s established socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught `AssertionError` that terminates the Node.js process. Both the HTTP/1.1 and HTTP/2 paths are affected.&lt;/p&gt;
&lt;p&gt;A malicious or compromised HTTPS endpoint reached through undici or the global `fetch()` can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process. Only TLS 1.2 is affected, because TLS 1.3 does not support renegotiation. Exploitation does not require a CA compromise: the attacker controls the endpoint and can present two ordinary valid certificates, the first matching the requested URL and the second intentionally not matching it.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Upgrade to undici 6.29.1, 7.30.1, or 8.12.2.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Restrict outbound connections to TLS 1.3, for example by setting `connect: { minVersion: &amp;#39;TLSv1.3&amp;#39;, maxVersion: &amp;#39;TLSv1.3&amp;#39; }` on the client or agent, so that renegotiation cannot occur, when the target endpoints support TLS 1.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qrxm-fqhp-jwvm</guid>
    </item>
    <item>
      <title>RHSA-2026:84657 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:84657</link>
      <description>&lt;p&gt;undici: undici: Denial of Service via TLS renegotiation with mismatched certificate undici: undici: Denial of Service via unhandled exception in decompress interceptor brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns undici: undici: Certificate validation bypass via dropped TLS options in Agent undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching undici: undici: Subresource Integrity bypass via non-lowercase algorithm tokens undici: undici: Denial of Service via unhandled stream error on excessive content encodings undici: undici: Denial of Service via memory exhaustion in EventSource client undici: undici: Denial of Service via unbounded WebSocket PONG buffering&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;undici: undici: Denial of Service via TLS renegotiation with mismatched certificate undici: undici: Denial of Service via unhandled exception in decompress interceptor brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns undici: undici: Certificate validation bypass via dropped TLS options in Agent undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching undici: undici: Subresource Integrity bypass via non-lowercase algorithm tokens undici: undici: Denial of Service via unhandled stream error on excessive content encodings undici: undici: Denial of Service via memory exhaustion in EventSource client undici: undici: Denial of Service via unbounded WebSocket PONG buffering&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:84657</guid>
    </item>
    <item>
      <title>RLSA-2026:96088 — Important: nodejs24 security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:96088</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: nodejs24&lt;/p&gt;
&lt;p&gt;Node.js is a platform built on Chrome&amp;#39;s JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)&lt;/p&gt;
&lt;p&gt;* brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)&lt;/p&gt;
&lt;p&gt;* undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)&lt;/p&gt;
&lt;p&gt;* undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)&lt;/p&gt;
&lt;p&gt;* undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)&lt;/p&gt;
&lt;p&gt;* undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)&lt;/p&gt;
&lt;p&gt;* nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames (CVE-2026-105483)&lt;/p&gt;
&lt;p&gt;* nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)&lt;/p&gt;
&lt;p&gt;* nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:Rocky Linux-295759)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a C…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: nodejs24&lt;/p&gt;
&lt;p&gt;Node.js is a platform built on Chrome&amp;#39;s JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)&lt;/p&gt;
&lt;p&gt;* brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)&lt;/p&gt;
&lt;p&gt;* undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)&lt;/p&gt;
&lt;p&gt;* undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)&lt;/p&gt;
&lt;p&gt;* undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)&lt;/p&gt;
&lt;p&gt;* undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)&lt;/p&gt;
&lt;p&gt;* nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames (CVE-2026-105483)&lt;/p&gt;
&lt;p&gt;* nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)&lt;/p&gt;
&lt;p&gt;* nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)&lt;/p&gt;
&lt;p&gt;Bug Fix(es) and Enhancement(s):&lt;/p&gt;
&lt;p&gt;* nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:Rocky Linux-295759)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a C…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:96088</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-87018</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-87018</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: node-undici, Ubuntu:26.10: node-undici, Ubuntu:26.04:LTS: node-undici&lt;/p&gt;
&lt;p&gt;undici is an HTTP client library for Node.js. In versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, the client process crashes when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with a certificate-altname error, but undici&amp;#39;s established-socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught assertion that terminates the Node.js process, affecting both the HTTP/1.1 and HTTP/2 paths. A malicious or compromised HTTPS endpoint reached through undici or the global fetch() can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process, and exploitation needs no CA compromise because the attacker controls the endpoint and can present two ordinary valid certificates. Only TLS 1.2 is affected, since TLS 1.3 does not support renegotiation. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. As a workaround, restrict outbound connections to TLS 1.3 so renegotiation cannot occur, when the target endpoints support it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: node-undici, Ubuntu:26.10: node-undici, Ubuntu:26.04:LTS: node-undici&lt;/p&gt;
&lt;p&gt;undici is an HTTP client library for Node.js. In versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, the client process crashes when a TLS 1.2 server renegotiates after the connection is established and presents a different, CA-trusted certificate whose hostname does not match the requested host. Node.js re-runs hostname verification on the renegotiated handshake and destroys the socket with a certificate-altname error, but undici&amp;#39;s established-socket error handler asserted that this error code could never occur, so the peer-controlled error became an uncaught assertion that terminates the Node.js process, affecting both the HTTP/1.1 and HTTP/2 paths. A malicious or compromised HTTPS endpoint reached through undici or the global fetch() can crash the client with a single server-initiated renegotiation, taking down all in-flight requests and background work in the process, and exploitation needs no CA compromise because the attacker controls the endpoint and can present two ordinary valid certificates. Only TLS 1.2 is affected, since TLS 1.3 does not support renegotiation. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to one of those versions or later. As a workaround, restrict outbound connections to TLS 1.3 so renegotiation cannot occur, when the target endpoints support it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-87018</guid>
    </item>
  </channel>
</rss>
