<?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>Tue, 17 Nov 2026 02:50:11 +0000</lastBuildDate>
    <item>
      <title>CLEANSTART-2026-MY20516 — Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-my20516</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: argo-workflows&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the argo-workflows package. Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: argo-workflows&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the argo-workflows package. Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-my20516</guid>
    </item>
    <item>
      <title>EUVD-2026-395623</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-395623</link>
      <description>EUVD-2026-395623</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-395623</guid>
    </item>
    <item>
      <title>fkie_cve-2026-118778</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-118778</link>
      <description>&lt;p&gt;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(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge&amp;#39;s TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge&amp;#39;s TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-118778</guid>
    </item>
    <item>
      <title>GHSA-525v-9gp9-w22h — Forge: TLS client crash when the server sends no certificate</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-525v-9gp9-w22h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-forge&lt;/p&gt;
&lt;p&gt;### Summary
The forge TLS client&amp;#39;s check for a missing server certificate read the wrong property and never ran. A malicious TLS server, or an on-path attacker who removes the server&amp;#39;s Certificate message, can make `connection.process()` throw a `TypeError`, which crashes applications that use the forge TLS client. Fixed in node-forge 1.4.1.&lt;/p&gt;
&lt;p&gt;### Details
After ServerHelloDone, `tls.handleServerHelloDone()` in `lib/tls.js` is meant to reject a server that sent no certificate with a fatal `insufficient_security` alert, after consulting the application&amp;#39;s `verify` callback. The check tested `c.serverCertificate`, which is never set (the certificate is stored as `c.session.serverCertificate`), so it never ran. The client state machine allows ServerHelloDone directly after ServerHello, so the handshake continued to `tls.createClientKeyExchange()`, which reads `c.session.serverCertificate.publicKey` and throws a `TypeError` on the null certificate. The exception propagates out of `connection.process()` without calling the `verify` or `error` callbacks.&lt;/p&gt;
&lt;p&gt;There is no authentication bypass: without a server certificate the client cannot build its RSA key exchange, so the handshake cannot complete.&lt;/p&gt;
&lt;p&gt;The fix reads `c.session.serverCertificate` and always fails the handshake in that case, still calling `verify` so the application can customize the alert. Failing even when `verify` returns `true` is needed because the key exchange requires the certificate.&lt;/p&gt;
&lt;p&gt;#### Patches
Fixed in node-forg…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-forge&lt;/p&gt;
&lt;p&gt;### Summary
The forge TLS client&amp;#39;s check for a missing server certificate read the wrong property and never ran. A malicious TLS server, or an on-path attacker who removes the server&amp;#39;s Certificate message, can make `connection.process()` throw a `TypeError`, which crashes applications that use the forge TLS client. Fixed in node-forge 1.4.1.&lt;/p&gt;
&lt;p&gt;### Details
After ServerHelloDone, `tls.handleServerHelloDone()` in `lib/tls.js` is meant to reject a server that sent no certificate with a fatal `insufficient_security` alert, after consulting the application&amp;#39;s `verify` callback. The check tested `c.serverCertificate`, which is never set (the certificate is stored as `c.session.serverCertificate`), so it never ran. The client state machine allows ServerHelloDone directly after ServerHello, so the handshake continued to `tls.createClientKeyExchange()`, which reads `c.session.serverCertificate.publicKey` and throws a `TypeError` on the null certificate. The exception propagates out of `connection.process()` without calling the `verify` or `error` callbacks.&lt;/p&gt;
&lt;p&gt;There is no authentication bypass: without a server certificate the client cannot build its RSA key exchange, so the handshake cannot complete.&lt;/p&gt;
&lt;p&gt;The fix reads `c.session.serverCertificate` and always fails the handshake in that case, still calling `verify` so the application can customize the alert. Failing even when `verify` returns `true` is needed because the key exchange requires the certificate.&lt;/p&gt;
&lt;p&gt;#### Patches
Fixed in node-forg…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-525v-9gp9-w22h</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-118778 — Forge: TLS client crash when the server sends no certificate</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-118778</link>
      <description>msrc_CVE-2026-118778</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-118778</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-118778</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-118778</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge&lt;/p&gt;
&lt;p&gt;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(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge&amp;#39;s TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-node-forge, Ubuntu:22.04:LTS: node-node-forge&lt;/p&gt;
&lt;p&gt;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(), c.session.serverCertificate, RSA key exchange to process the relevant input or security decision. node-forge&amp;#39;s TLS client checked the wrong property when deciding whether a server certificate was missing. A malicious TLS server or on-path peer could omit the Certificate message and reach code that dereferenced the absent certificate, causing an uncaught exception and terminating the connection or process. This issue is fixed in version 1.4.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-118778</guid>
    </item>
  </channel>
</rss>
