Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-mhvj-jhpq-885v

blaze: Multiple HTTP/1.1 request-smuggling primitives in blaze's Java wire parser

CVSS 7.4 HighEPSS 0.0063 · 50th percentile

Published by the GitHub Advisory Database at 24 Jul 2026, 22:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.http4s:http4s-blaze-server_2.13Maven<0.23.180.23.18
org.http4s:blaze-http_2.13Maven<0.23.18 || >=1.0.0-M1, <1.0.0-M420.23.18, 1.0.0-M42
org.http4s:blaze-http_3Maven<0.23.18 || >=1.0.0-M1, <1.0.0-M420.23.18, 1.0.0-M42
Identifiers
GHSA-mhvj-jhpq-885v · CVE-2026-73494
Weakness (CWE)
CWE-444
Tags
Published
24 Jul 2026
Updated
12 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-mhvj-jhpq-885v affects blaze's Java HTTP/1.1 wire parser in several Maven packages: org.http4s:http4s-blaze-server_2.13 before 0.23.18, org.http4s:blaze-http_2.13 before 0.23.18 and from 1.0.0-M1 to before 1.0.0-M42, and org.http4s:blaze-http_3 with the same ranges. Exploitation requires a fronting proxy that parses malformed requests differently from blaze, letting an attacker bypass front-end access controls or poison responses and caches. Upgrade to 0.23.18 or 1.0.0-M42. Deploying behind a strict reverse proxy that rejects malformed requests is a workaround.

Written 2 Nov 2026.

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

ScoreRatingCVSSVectorSource
7.4 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0063, the 50th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.