CVE-2025-58369: FS2 half-shutdown of socket during TLS handshake may result in spin loop on opposite side
When establishing a TLS session using fs2-io on the JVM using the fs2.io.net.tls package, if one side of the connection shuts down write while the peer side is awaiting more data to progress the TLS handshake, the peer side will spin loop on the socket read, fully utilizing a CPU. This CPU is consumed until the overall connection is closed.
This could be used as a denial of service attack on an fs2-io powered server – for example, by opening many connections and putting them in a half-shutdown state.
Note: this issue impacts ember backed http4s servers with HTTPS as a result of ember using fs2’s TLS support.
References
- github.com/advisories/GHSA-rrw2-px9j-qffj
- github.com/typelevel/fs2
- github.com/typelevel/fs2/commit/46e2dc3abf994dcf3d0b804b2ddb3c10c04d4976
- github.com/typelevel/fs2/commit/5c6c4c6c1ef330f7e6b53661ecc63d5f5ba8885c
- github.com/typelevel/fs2/issues/3590
- github.com/typelevel/fs2/releases/tag/v3.12.2
- github.com/typelevel/fs2/releases/tag/v3.13.0-M7
- github.com/typelevel/fs2/security/advisories/GHSA-rrw2-px9j-qffj
- nvd.nist.gov/vuln/detail/CVE-2025-58369
Code Behaviors & Features
Detect and mitigate CVE-2025-58369 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →