cve.bz

CVE-2026-73493 http4s blaze

7.5 highEPSS 0.6%Fix available

High (7.5) in http4s blaze. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.http4s:http4s-blaze-server_2.13 0.23.18, 1.0.0-M42.

On this page
Http4s (http4s-blaze-server) is a minimal, idiomatic Scala interface for HTTP services. Prior to 0.23.18 and 1.0.0-M42, http4s-blaze-server aggregates fragments of an incoming WebSocket message with no limit on total size or fragment count. A client that completes a WebSocket handshake can send an unterminated fragmented message and drive unbounded heap growth in the server JVM, resulting in denial of service through OutOfMemoryError. Any http4s application serving WebSocket routes over BlazeServerBuilder is affected, no non-default configuration is required, and maxWebSocketBufferSize does not bound the aggregate because it bounds only individual frames. A single connection sending continuation frames that never set FIN forces the server to buffer every fragment until the heap is exhausted, terminating the JVM with OutOfMemoryError on the blaze selector thread. Small fragments amplify the cost through per-frame object overhead, so a modest volume of wire bytes is sufficient. This issue is fixed in versions 0.23.18 and 1.0.0-M42.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-13. 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-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • org.http4s:http4s-blaze-server_2.13 (Maven): fixed in 0.23.18, 1.0.0-M42
  • org.http4s:http4s-blaze-server_2.12 (Maven): fixed in 0.23.18
  • org.http4s:http4s-blaze-server_3 (Maven): fixed in 1.0.0-M42

Ask an AI about this CVE

Show the promptExplain CVE-2026-73493 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73493?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73493?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-2026-73493 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
http4s blaze< 0.23.18
http4s blaze>= 1.0.0-M1, < 1.0.0-M42

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7ppr-r889-mcf2Mavenorg.http4s:http4s-blaze-server_2.13<0.23.180.23.18
GHSA-7ppr-r889-mcf2Mavenorg.http4s:http4s-blaze-server_2.13>=1.0.0-M1 <1.0.0-M421.0.0-M42
GHSA-7ppr-r889-mcf2Mavenorg.http4s:http4s-blaze-server_2.12<0.23.180.23.18
GHSA-7ppr-r889-mcf2Mavenorg.http4s:http4s-blaze-server_3>=1.0.0-M1 <1.0.0-M421.0.0-M42

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON