<?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-16T20:51:12.356638+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/bell-cve-2026-123868</id>
    <title>BELL-CVE-2026-123868</title>
    <updated>2026-11-16T20:51:12.368104+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: nodejs22, Alpaquita:25: nodejs24, Alpaquita:25: nodejs26, Alpaquita:stream: nodejs22, Alpaquita:stream: nodejs24, Alpaquita:stream: nodejs26, BellSoft Hardened Containers:25: nodejs22, BellSoft Hardened Containers:25: nodejs24, BellSoft Hardened Containers:25: nodejs26, BellSoft Hardened Containers:stream: nodejs22 and 2 more</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-123868"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1531</id>
    <title>certfr-2026-avi-1531 — De multiples vulnérabilités ont été découvertes dans Node.js. Certaines d'entre elles permettent à un attaquant de prov…</title>
    <updated>2026-11-16T20:51:12.368175+00:00</updated>
    <content>certfr-2026-avi-1531</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1531"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-405160</id>
    <title>EUVD-2026-405160</title>
    <updated>2026-11-16T20:51:12.368196+00:00</updated>
    <content>EUVD-2026-405160</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-405160"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123868</id>
    <title>fkie_cve-2026-123868</title>
    <updated>2026-11-16T20:51:12.368208+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-123868"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fxrg-pjjh-rp27</id>
    <title>GHSA-fxrg-pjjh-rp27</title>
    <updated>2026-11-16T20:51:12.368237+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fxrg-pjjh-rp27"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ncsc-2026-0492</id>
    <title>NCSC-2026-0492 — Kwetsbaarheden verholpen in Node.js</title>
    <updated>2026-11-16T20:51:12.368260+00:00</updated>
    <content>NCSC-2026-0492</content>
    <link href="https://cve.radiocsirt.org/vuln/ncsc-2026-0492"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:93603</id>
    <title>RHSA-2026:93603 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
    <updated>2026-11-16T20:51:12.368293+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>minimatch: minimatch: Denial of Service via crafted glob pattern expansion nodejs: nodejs: Denial of Service via HTTP/2 Alt-Svc heap buffer overflow nodejs: Node.js: Denial of Service via improper HTTP/2 session teardown nodejs: nodejs: Denial of service via HTTP/2 memory exhaustion nodejs: nodejs: Denial of Service via HTTP/2 use-after-free nodejs: nodejs: Denial of service via premature socket closure during TLS handshake</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:93603"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123868</id>
    <title>UBUNTU-CVE-2026-123868</title>
    <updated>2026-11-16T20:51:12.368333+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123868"/>
  </entry>
</feed>
