Allocation of Resources Without Limits or Throttling Affecting org.http4s:http4s-blaze-server_2.12 package, versions [,0.23.18)[1.0.0-M2,]
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGHTTP4S-18313134
- published26 Jul 2026
- disclosed24 Jul 2026
- creditUnknown
Introduced: 24 Jul 2026
NewCVE-2026-73493 (opens in a new tab)How to fix?
A fix was pushed into the master branch but not yet published.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the aggregation of incoming WebSocket message fragments without any limit on total size or fragment count. An attacker can exhaust server memory and cause a denial of service by sending a continuous stream of fragmented WebSocket messages that never complete, leading to unbounded heap growth and eventual server termination.
Workaround
This vulnerability can be mitigated by terminating or limiting WebSocket traffic at a fronting layer that enforces message-size and fragment limits, or by disabling WebSocket routes.