Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
fs2-io versions 3.1.0 up to but not including 3.2.11 (Maven co.fs2 packages, including the Scala-versioned fs2-io artifacts) are affected when running on Node.js. In server-mode TLS sockets with requestCert set to true, peer certificate verification is skipped, so an attacker can connect without a valid client certificate and the connection is accepted. Upgrade to fs2-io 3.2.11 or later. If you cannot upgrade, do not use server-mode TLS sockets with requestCert set to true on Node.js.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.1 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0083, the 58th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:10 UTC First seen by agentprime
- 31 Oct 2026, 15:10 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2cpx-6pqp-wf35
- OSV: GHSA-2cpx-6pqp-wf35
- github.com/typelevel/fs2/security/advisories/GHSA-2cpx-6pqp-wf35
- nvd.nist.gov/vuln/detail/CVE-2022-31183
- github.com/nodejs/node/issues/43994
- github.com/typelevel/fs2/commit/19ce392e8093d9571387dbd78e159e655a85aeea
- github.com/typelevel/fs2/commit/659824395826a314e0a4331535dbf1ef8bef8207
- github.com/typelevel/fs2
- github.com/typelevel/fs2/releases/tag/v3.2.11