https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T06:37:38.194703+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-232661 EUVD-2026-232661 2026-10-04T06:37:38.258994+00:00 EUVD-2026-232661 https://cve.radiocsirt.org/vuln/fkie_cve-2022-31183 fkie_cve-2022-31183 2026-10-04T06:37:38.259031+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-2cpx-6pqp-wf35 GHSA-2cpx-6pqp-wf35 — fs2-io skips mTLS client verification 2026-10-04T06:37:38.259068+00:00

Affected: 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

### Impact

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 v3.1.0.

### Patches

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.

### Workarounds

If using an unpatched version on Node.js, do not use a server-mode `TLSSocket` with `requestCert = true` to establish a mTLS connection.

### References - https://github.com/nodejs/node/issues/43994 - https://www.cloudflare.com/learning/access-management/what-is-mutual-tls/

### 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).

 https://cve.radiocsirt.org/vuln/gsd-2022-31183 gsd-2022-31183 2026-10-04T06:37:38.259114+00:00 gsd-2022-31183