Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of http4s-blaze-server before 0.23.18, and from 1.0.0-M1 up to but not including 1.0.0-M42, are affected. A client that completes a WebSocket handshake can send a fragmented message that is never terminated, forcing the server to buffer fragments without limit until the JVM runs out of memory and crashes. Upgrade to 0.23.18 or 1.0.0-M42. No configuration option bounds the buffering, so the only listed workaround is to limit WebSocket traffic at a fronting layer or disable WebSocket routes.
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 |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0063, the 50th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:19 UTC First seen by agentprime
- 31 Oct 2026, 14:19 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-7ppr-r889-mcf2
- OSV: GHSA-7ppr-r889-mcf2
- github.com/http4s/blaze/security/advisories/GHSA-7ppr-r889-mcf2
- github.com/http4s/blaze/commit/173e8ca820a0d12110bfe409c72e9b9c3d28d471
- github.com/http4s/blaze/commit/2ae13a74d55209b6573d5228d1aa94f0361a75d0
- github.com/http4s/blaze/commit/fadbe6d0f7f59045425688d313c8d4804973d12f
- github.com/http4s/blaze
- github.com/http4s/blaze/releases/tag/v0.23.18
- github.com/http4s/blaze/releases/tag/v1.0.0-M42