<?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-17T04:47:54.628934+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/cleanstart-2026-oj51387</id>
    <title>CLEANSTART-2026-OJ51387 — Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript</title>
    <updated>2026-11-17T04:47:54.633902+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: argo-workflows</p>
<p>Security vulnerability affects the argo-workflows package. Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-oj51387"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396532</id>
    <title>EUVD-2026-396532</title>
    <updated>2026-11-17T04:47:54.633951+00:00</updated>
    <content>EUVD-2026-396532</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396532"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-119188</id>
    <title>fkie_cve-2026-119188</title>
    <updated>2026-11-17T04:47:54.633967+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), fragmented handshake message, interleaved record to process the relevant input or security decision. node-forge continued processing after a TLS record of another content type interrupted a fragmented handshake message. A remote peer could trigger an uncaught TypeError in process(), causing the connection or hosting process to fail. This issue is fixed in version 1.4.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-119188"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8hrf-8g6f-7xwp</id>
    <title>GHSA-8hrf-8g6f-7xwp — Forge: Denial of service in TLS record processing via a record interleaved with a fragmented handshake message</title>
    <updated>2026-11-17T04:47:54.633992+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: node-forge</p>
<p>### Summary</p>
<p>A connection created with `forge.tls.createConnection()` throws an uncaught `TypeError` from `process()` when it receives a record of another content type while waiting for the rest of a handshake message that was split across records. A peer can trigger this with 18 bytes before the handshake, without authentication, which terminates Node.js processes that use the documented socket wiring. Fixed in node-forge 1.4.1.</p>
<p>### Details</p>
<p>In `lib/tls.js`, `_readRecord()` handles a record that arrives while a handshake message split across records is incomplete. If the record has any other content type (change_cipher_spec, alert, application_data or heartbeat), forge correctly reports "Invalid fragmented record." through `c.error()` with a fatal `unexpected_message` alert. That fatal error closes and resets the connection, which sets `c.record` to `null`. `_readRecord()` then continues with `c.record.ready = true` and throws `TypeError: Cannot set properties of null (setting 'ready')` out of `process()`. The code is unchanged since the first release.</p>
<p>RFC 5246 section 6.2.1 allows a handshake message to be fragmented across records, and RFC 8446 section 5.1 forbids interleaving handshake messages with other record types. Failing the connection with `unexpected_message` is the intended behavior; the bug is the crash after the error.</p>
<p>node-forge reports TLS protocol errors through the `error` callback, so applications do not normally wrap `process()` in `try`/`catch`. When…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8hrf-8g6f-7xwp"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-119188</id>
    <title>msrc_CVE-2026-119188 — Forge: Denial of service in TLS record processing via a record interleaved with a fragmented handshake message</title>
    <updated>2026-11-17T04:47:54.634038+00:00</updated>
    <content>msrc_CVE-2026-119188</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-119188"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-119188</id>
    <title>UBUNTU-CVE-2026-119188</title>
    <updated>2026-11-17T04:47:54.634055+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge</p>
<p>Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), fragmented handshake message, interleaved record to process the relevant input or security decision. node-forge continued processing after a TLS record of another content type interrupted a fragmented handshake message. A remote peer could trigger an uncaught TypeError in process(), causing the connection or hosting process to fail. This issue is fixed in version 1.4.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-119188"/>
  </entry>
</feed>
