<?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>Sun, 04 Oct 2026 01:22:37 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-232661</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232661</link>
      <description>EUVD-2026-232661</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232661</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31183</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31183</link>
      <description>&lt;p&gt;fs2 is a compositional, streaming I/O library for Scala. When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds. The vulnerability is limited to: 1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent. 2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API. 3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s. It was introduced with the initial Node.js implementation of fs2-io in 3.1.0. A patch is released in v3.2.11. The requestCert = true parameter is respected and the peer certificate is verified. If verification fails, a SSLException is raised. If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fs2 is a compositional, streaming I/O library for Scala. When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds. The vulnerability is limited to: 1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent. 2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API. 3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s. It was introduced with the initial Node.js implementation of fs2-io in 3.1.0. A patch is released in v3.2.11. The requestCert = true parameter is respected and the peer certificate is verified. If verification fails, a SSLException is raised. If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31183</guid>
    </item>
    <item>
      <title>GHSA-2cpx-6pqp-wf35 — fs2-io skips mTLS client verification</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2cpx-6pqp-wf35</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: co.fs2:fs2-io, Maven: co.fs2:fs2-io_2.12, Maven: co.fs2:fs2-io_3, Maven: co.fs2:fs2-io_2.13, Maven: co.fs2:fs2-io_sjs1_2.13, Maven: co.fs2:fs2-io_sjs1_3&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds.&lt;/p&gt;
&lt;p&gt;The vulnerability is limited to:
1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent.
2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API.
3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s.&lt;/p&gt;
&lt;p&gt;It was introduced with the initial Node.js implementation of fs2-io in v3.1.0.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch is released in v3.2.11. The `requestCert = true` parameter is respected and the peer certificate is verified. If verification fails, a `SSLException` is raised.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If using an unpatched version on Node.js, do not use a server-mode `TLSSocket` with `requestCert = true` to establish a mTLS connection.&lt;/p&gt;
&lt;p&gt;### References
- https://github.com/nodejs/node/issues/43994
- https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* [Open an issue.](https://github.com/typelevel/fs2/issues/new/choose)
* Contact the [Typelevel Security Team](https://github.com/typelevel/.github/blob/main/SECURITY.md).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: co.fs2:fs2-io, Maven: co.fs2:fs2-io_2.12, Maven: co.fs2:fs2-io_3, Maven: co.fs2:fs2-io_2.13, Maven: co.fs2:fs2-io_sjs1_2.13, Maven: co.fs2:fs2-io_sjs1_3&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds.&lt;/p&gt;
&lt;p&gt;The vulnerability is limited to:
1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent.
2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API.
3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s.&lt;/p&gt;
&lt;p&gt;It was introduced with the initial Node.js implementation of fs2-io in v3.1.0.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;A patch is released in v3.2.11. The `requestCert = true` parameter is respected and the peer certificate is verified. If verification fails, a `SSLException` is raised.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If using an unpatched version on Node.js, do not use a server-mode `TLSSocket` with `requestCert = true` to establish a mTLS connection.&lt;/p&gt;
&lt;p&gt;### References
- https://github.com/nodejs/node/issues/43994
- https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* [Open an issue.](https://github.com/typelevel/fs2/issues/new/choose)
* Contact the [Typelevel Security Team](https://github.com/typelevel/.github/blob/main/SECURITY.md).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2cpx-6pqp-wf35</guid>
    </item>
    <item>
      <title>gsd-2022-31183</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31183</link>
      <description>gsd-2022-31183</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31183</guid>
    </item>
  </channel>
</rss>
