CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LMedium (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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lco.fs2:fs2-io_2.12 (Maven): fixed in 3.12.2, 3.13.0-M7, 2.5.13co.fs2:fs2-io_2.13 (Maven): fixed in 3.12.2, 3.13.0-M7, 2.5.13co.fs2:fs2-io_3 (Maven): fixed in 3.12.2, 3.13.0-M7, 2.5.13Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| typelevel fs2 | >= 3.0.0-M1, < 3.12.2 |
| typelevel fs2 | >= 3.13.0-M1, < 3.13.0-M7 |
| typelevel fs2 | < 2.5.13 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12 | >=3.0.0-M1 <3.12.2 | 3.12.2 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12 | >=3.13.0-M1 <3.13.0-M7 | 3.13.0-M7 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.13 | >=3.0.0-M1 <3.12.2 | 3.12.2 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.13 | >=3.13.0-M1 <3.13.0-M7 | 3.13.0-M7 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_3 | >=3.0.0-M1 <3.12.2 | 3.12.2 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_3 | >=3.13.0-M1 <3.13.0-M7 | 3.13.0-M7 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_0.26 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_0.27 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.11 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12.0-M4 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12.0-RC1 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12.0-M5 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12.0-RC2 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.13.0-M5 | all versions | no fix published |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.12 | <2.5.13 | 2.5.13 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_2.13 | <2.5.13 | 2.5.13 |
| GHSA-rrw2-px9j-qffj | Maven | co.fs2:fs2-io_3 | <2.5.13 | 2.5.13 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.