<?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:36:03.786063+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-123877</id>
    <title>BELL-CVE-2026-123877</title>
    <updated>2026-11-16T20:36:03.796510+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-123877"/>
  </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:36:03.796572+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-405165</id>
    <title>EUVD-2026-405165</title>
    <updated>2026-11-16T20:36:03.796592+00:00</updated>
    <content>EUVD-2026-405165</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-405165"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-123877</id>
    <title>fkie_cve-2026-123877</title>
    <updated>2026-11-16T20:36:03.796603+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-123877"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4g6g-xjc7-fh73</id>
    <title>GHSA-4g6g-xjc7-fh73</title>
    <updated>2026-11-16T20:36:03.796629+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4g6g-xjc7-fh73"/>
  </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:36:03.796648+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:99433</id>
    <title>RHSA-2026:99433 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
    <updated>2026-11-16T20:36:03.796676+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>nodejs: Node.js: Information disclosure via improper permission checks in recursive file watching nodejs: Node.js: Denial of service via abrupt disconnection during zlib compression nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy nodejs: Node.js: Denial of service via HTTP/2 session resource leak during shutdown nodejs: Node.js: Information disclosure via use-after-free during HTTP/2 stream teardown nodejs: Node.js: Mutual TLS authorization bypass via incomplete SNI context configuration nodejs: Node.js: Information disclosure via invalid proxy configuration error messages nodejs: Node.js: Client certificate authentication bypass via TLS renegotiation nodejs: nodejs: Denial of Service via cancelled HTTP/2 file downloads nodejs: nodejs: Certificate validation bypass via TLS session cache reuse</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:99433"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123877</id>
    <title>UBUNTU-CVE-2026-123877</title>
    <updated>2026-11-16T20:36:03.796707+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>A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-123877"/>
  </entry>
</feed>
