<?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-16T21:44:37.145955+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/alsa-2026:96088</id>
    <title>ALSA-2026:96088 — Important: nodejs24 security, bug fix, and enhancement update</title>
    <updated>2026-11-16T21:44:37.753852+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:10: nodejs24-docs, AlmaLinux:10: nodejs24-npm</p>
<p>Node.js is a platform built on Chrome'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.</p>
<p>Security Fix(es):</p>
<p>* 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)</p>
<p>Bug Fix(es) and Enhancement(s):</p>
<p>* nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:RHEL-295759)</p>
<p>For more details about the security issue(s), including th…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/alsa-2026:96088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1539</id>
    <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>
    <updated>2026-11-16T21:44:37.754036+00:00</updated>
    <content>certfr-2026-avi-1539</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1539"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-la92040</id>
    <title>CLEANSTART-2026-LA92040 — undici is an HTTP client library for Node</title>
    <updated>2026-11-16T21:44:37.754058+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: npm</p>
<p>Security vulnerability affects the npm package. undici is an HTTP client library for Node.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-la92040"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-388465</id>
    <title>EUVD-2026-388465</title>
    <updated>2026-11-16T21:44:37.754080+00:00</updated>
    <content>EUVD-2026-388465</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-388465"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-109383</id>
    <title>fkie_cve-2026-109383</title>
    <updated>2026-11-16T21:44:37.754092+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>undici is an HTTP client library for Node.js. In versions 4.0.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its Agent dispatcher passes its constructor options through a JSON-based deep clone before forwarding them to each per-origin pool, and because JSON cannot represent functions, a caller-supplied tls option containing a checkServerIdentity callback is silently dropped before it reaches the TLS layer. As a result, a TLS peer whose certificate a custom checkServerIdentity was written to reject, but which passes Node's default hostname and chain checks, is silently accepted. Because Agent is the default dispatcher behind request, fetch, and setGlobalDispatcher, this affects the path most applications use, and EnvHttpProxyAgent is affected on its direct and no-proxy routes as well, while only applications that pass a function-valued tls option such as a custom checkServerIdentity for certificate or public-key pinning are at risk. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which preserve the tls option outside the JSON clone so custom verification callbacks are forwarded unchanged, and users should upgrade to one of those versions or later. As a workaround, pass the TLS options through connect instead of tls, or for proxied destinations use requestTls and proxyTls.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-109383"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2m5v-pch6-74hx</id>
    <title>GHSA-2m5v-pch6-74hx — undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent</title>
    <updated>2026-11-16T21:44:37.754123+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: undici</p>
<p>### Impact</p>
<p>undici's `Agent` passes its constructor options through a JSON-based deep clone (`JSON.parse(JSON.stringify(...))`) before forwarding them to each per-origin `Pool`. JSON cannot represent functions, so a caller-supplied `tls` option containing a `checkServerIdentity` callback is silently dropped before it reaches the TLS layer. As a result, a TLS peer whose certificate a custom `checkServerIdentity` was written to reject, but which passes Node's default hostname and chain checks, is silently accepted when the request is made through `Agent`. Because `Agent` is the default dispatcher behind `request`, `fetch`, and `setGlobalDispatcher`, this is the path most applications use. `EnvHttpProxyAgent` is also affected on its direct and `NO_PROXY` routes, which delegate to an internal `Agent`.</p>
<p>Only applications that pass a function-valued `tls` option (such as a custom `checkServerIdentity` for certificate or public-key pinning) are affected. Passing the same options through `connect` is not affected. This is the `Agent` counterpart of the `BalancedPool` certificate validation bypass fixed in CVE-2026-84961.</p>
<p>### Patches</p>
<p>Upgrade to undici `6.29.1`, `7.30.1`, or `8.12.2`. `Agent` now preserves the `tls` option outside the JSON clone, so custom TLS verification callbacks are forwarded to each origin unchanged.</p>
<p>### Workarounds</p>
<p>Pass the TLS options through `connect` instead of `tls`. For proxied `EnvHttpProxyAgent` destinations, use `requestTls` / `proxyTls`.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2m5v-pch6-74hx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:84657</id>
    <title>RHSA-2026:84657 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
    <updated>2026-11-16T21:44:37.754158+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:84657"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rlsa-2026:96088</id>
    <title>RLSA-2026:96088 — Important: nodejs24 security, bug fix, and enhancement update</title>
    <updated>2026-11-16T21:44:37.754253+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: nodejs24</p>
<p>Node.js is a platform built on Chrome'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.</p>
<p>Security Fix(es):</p>
<p>* brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)</p>
<p>* brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)</p>
<p>* undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)</p>
<p>* undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)</p>
<p>* undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)</p>
<p>* undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)</p>
<p>* nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames (CVE-2026-105483)</p>
<p>* nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)</p>
<p>* nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)</p>
<p>Bug Fix(es) and Enhancement(s):</p>
<p>* nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:Rocky Linux-295759)</p>
<p>For more details about the security issue(s), including the impact, a C…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rlsa-2026:96088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-109383</id>
    <title>UBUNTU-CVE-2026-109383</title>
    <updated>2026-11-16T21:44:37.754367+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: node-undici, Ubuntu:26.10: node-undici, Ubuntu:26.04:LTS: node-undici</p>
<p>undici is an HTTP client library for Node.js. In versions 4.0.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its Agent dispatcher passes its constructor options through a JSON-based deep clone before forwarding them to each per-origin pool, and because JSON cannot represent functions, a caller-supplied tls option containing a checkServerIdentity callback is silently dropped before it reaches the TLS layer. As a result, a TLS peer whose certificate a custom checkServerIdentity was written to reject, but which passes Node's default hostname and chain checks, is silently accepted. Because Agent is the default dispatcher behind request, fetch, and setGlobalDispatcher, this affects the path most applications use, and EnvHttpProxyAgent is affected on its direct and no-proxy routes as well, while only applications that pass a function-valued tls option such as a custom checkServerIdentity for certificate or public-key pinning are at risk. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which preserve the tls option outside the JSON clone so custom verification callbacks are forwarded unchanged, and users should upgrade to one of those versions or later. As a workaround, pass the TLS options through connect instead of tls, or for proxied destinations use requestTls and proxyTls.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-109383"/>
  </entry>
</feed>
