CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-47073 remediation guide

benoitc hackney

Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The WebSocket client in src/hackney_ws.erl imposes no upper bound on memory consumption in three code paths. First, read_handshake_response/3 accumulates received bytes into a growing buffer with no size cap; the per-receive timeout resets on every chunk, so a server that streams bytes without ever sending \r\n\r\n causes the buffer to grow until memory is exhausted. Second, parse_payload/9 and parse_active_payload/8 do not validate the declared frame payload length against any limit; beca...

Open CVE record
Productbenoitc hackney
Affected versions>= 2.0.0 < 4.0.1, >= 690cecaf236fba49526da404a5bc889a24367a3e < ce0109e2970ace6e20ff29bae9d05c3ac22ec6dc
Fixed versions4.0.1
Priority basisReview · CVSS 8.7 · EPSS 0.85%
01

Identify the affected asset

Confirm whether benoitc hackney is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 2.0.0 < 4.0.1, >= 690cecaf236fba49526da404a5bc889a24367a3e < ce0109e2970ace6e20ff29bae9d05c3ac22ec6dc. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 4.0.1. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-47073 Remediation Guide | SECUFOCUS NOW