Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-73493 high CVSS 7.5

Vulnerability in org.http4s:http4s-blaze-server_2.13 (CVE-2026-73493)

Summary

vulnerability in org.http4s:http4s-blaze-server_2.13 (CVE-2026-73493). Risk of unauthorized operations or information disclosure. Exploitable via ``OutOfMemoryError``. Mitigation: upgrade to `1.0.0-M42` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-73493** has been found in org.http4s:http4s-blaze-server_2.13. Attackers can target a specific entry point like ``OutOfMemoryError`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10. What to do: upgrade org.http4s:http4s-blaze-server_2.13 to **1.0.0-M42** or later. If unsure, ask your IT team or search "org.http4s:http4s-blaze-server_2.13 CVE-2026-73493" on the vendor's site.
CVE-2026-73493 (org.http4s:http4s-blaze-server_2.13) — CWE-770 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `OutOfMemoryError` / `BlazeServerBuilder` / `maxWebSocketBufferSize` Patched: `1.0.0-M42` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-770) exists in org.http4s:http4s-blaze-server_2.13. Attackers reach the vulnerable code path via ``OutOfMemoryError`` without authentication.
📍 Affected scope
org.http4s:http4s-blaze-server_2.13 — . Attack surface: `OutOfMemoryError` / `BlazeServerBuilder` / `maxWebSocketBufferSize`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.0.0-M42**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.http4s:http4s-blaze-server_2.13' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'org.http4s:http4s-blaze-server_2.13' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.http4s:http4s-blaze-server_2.13` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade org.http4s:http4s-blaze-server_2.13 to 1.0.0-M42

    ステージング環境で 1.0.0-M42 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.http4s:http4s-blaze-server_2.13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M42"}]}]
maven org.http4s:http4s-blaze-server_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.18"}]}]
maven org.http4s:http4s-blaze-server_3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M42"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →