Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-71380 – Denial of Service (Slowloris-style Worker Exhaustion) – Erlang/OTP inets httpd Serv

Be the first to know when new zero-days emerge:

Summary

CVE-2026-71380 is a Missing Release of Resource after Effective Lifetime (CWE-772) vulnerability in the httpd component of Erlang/OTP’s inets HTTP server. It allows an unauthenticated, remote attacker to cause a denial of service by sending a well-formed HTTP request with a large Content-Length header and then stalling before delivering the full request body, permanently parking a server worker. The issue carries a CVSS score of 8.7 (High) and affects a wide range of OTP releases.

Technical details

  • Root cause: httpd_request_handler:handle_info/2 cancels the request timeout as soon as any parse step succeeds — including just parsing the headers — and the code path that re-arms the socket for more data ({active, once}) does not set a new timer.
  • Trigger conditions: httpd_request:whole_body/2 returns a "need more data" continuation whenever fewer bytes have arrived than the declared Content-Length. If the client simply stops sending data after headers are parsed, the worker is left waiting indefinitely because no timer is active.
  • Missing safety net: A periodic byte-rate check (minimum_bytes_per_second) exists to reclaim stalled connections, but it is disabled by default and must be explicitly configured.
  • Attack vector: Network, unauthenticated, low complexity — the attacker only needs to open a TCP connection, send valid headers with a large Content-Length, and stop sending body data.
  • Impact: Each stalled connection permanently occupies one worker slot. Repeating this across enough connections exhausts all workers allowed by max_clients, denying service to legitimate clients at negligible bandwidth/compute cost to the attacker (a Slowloris-style resource exhaustion attack).

Affected software

  • Erlang/OTP from 17.0 before 27.3.4.17
  • Erlang/OTP from 28.0 before 28.5.0.6
  • Erlang/OTP from 29.0 before 29.0.6
  • Corresponding inets application versions: from 5.10 before 9.3.2.7, from 9.4 before 9.6.2.3, and from 9.7 before 9.7.2
  • Whether OTP releases before 17.0 (inets before 5.10) are affected is unknown/unconfirmed by the vendor
  • Only deployments running the inets httpd HTTP server module are affected

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • Impact is limited to availability (no confidentiality or integrity impact)

Mitigation and recommended actions

  • Immediate (patch): Upgrade Erlang/OTP to 27.3.4.17, 28.5.0.6, or 29.0.6 (or later), depending on your current release line.
  • If patching is not immediately possible:
    • Configure minimum_bytes_per_second in the httpd configuration (e.g., {minimum_bytes_per_second, 200}) to enable the periodic byte-rate check that terminates stalled connections and reclaims parked workers. This check is off by default.
    • Place a reverse proxy (e.g., nginx) in front of httpd and enforce a strict body-read timeout (e.g., client_body_timeout) at the proxy layer.
    • Restrict network access to the httpd service to trusted clients/networks where feasible.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge