cve.bz

CVE-2025-58369 typelevel fs2: Uncontrolled Resource Consumption

5.3 mediumEPSS 0.5%Fix available

Medium (5.3) in typelevel fs2. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in co.fs2:fs2-io_2.12 2.5.13, 3.12.2, 3.13.0-M7.

On this page
fs2 is a compositional, streaming I/O library for Scala. Versions up to and including 2.5.12, 3.0.0-M1 through 3.12.2, and 3.13.0-M1 through 3.13.0-M6 are vulnerable to denial of service attacks though TLS sessions using fs2-io on the JVM using the fs2.io.net.tls package. When establishing a TLS session, 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. The CPU is consumed until the overall connection is closed, potentially shutting down a fs2-io powered server. This issue is fixed in versions 2.5.13, 3.12.1, and 3.13.0-M7.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-09-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • co.fs2:fs2-io_2.12 (Maven): fixed in 3.12.2, 3.13.0-M7, 2.5.13
  • co.fs2:fs2-io_2.13 (Maven): fixed in 3.12.2, 3.13.0-M7, 2.5.13
  • co.fs2:fs2-io_3 (Maven): fixed in 3.12.2, 3.13.0-M7, 2.5.13

Ask an AI about this CVE

Show the promptExplain CVE-2025-58369 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-58369?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-58369?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-58369 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
typelevel fs2>= 3.0.0-M1, < 3.12.2
typelevel fs2>= 3.13.0-M1, < 3.13.0-M7
typelevel fs2< 2.5.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12>=3.0.0-M1 <3.12.23.12.2
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12>=3.13.0-M1 <3.13.0-M73.13.0-M7
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.13>=3.0.0-M1 <3.12.23.12.2
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.13>=3.13.0-M1 <3.13.0-M73.13.0-M7
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_3>=3.0.0-M1 <3.12.23.12.2
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_3>=3.13.0-M1 <3.13.0-M73.13.0-M7
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_0.26all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_0.27all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.11all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12.0-M4all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12.0-RC1all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12.0-M5all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12.0-RC2all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.13.0-M5all versionsno fix published
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.12<2.5.132.5.13
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_2.13<2.5.132.5.13
GHSA-rrw2-px9j-qffjMavenco.fs2:fs2-io_3<2.5.132.5.13

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON