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

New CVE Detected

CVE-2026-70399 – Unauthenticated Denial of Service – Erlang/OTP inets httpd Module

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

Summary

CVE-2026-70399 is a resource-exhaustion (CWE-770: Allocation of Resources Without Limits or Throttling) vulnerability in the inets httpd HTTP server component of Erlang/OTP. Due to a coding defect in the connection-acceptance logic, servers that do not explicitly configure the max_clients option silently accept an unlimited number of simultaneous connections instead of enforcing the documented default limit of 150. An unauthenticated remote attacker can exploit this by opening a large number of connections, causing denial of service through exhaustion of server processes, memory, and file descriptors. The issue carries a CVSS v4.0 base score of 8.7 (High).

Technical details

  • Root cause: The connection accept gate in httpd_manager:handle_new_connection/4 retrieves the max_clients setting using httpd_util:lookup/2 (a two-argument lookup with no default), which returns the atom undefined when the option is not explicitly configured, rather than falling back to the documented default of 150.
  • Trigger condition: Because Erlang’s standard term ordering places all integers before all atoms, the comparison Count =< Max evaluates as true for any connection count when Max is undefined. As a result, the server’s {reject, busy} safeguard never triggers, and the connection limit is effectively bypassed on any httpd instance that has not explicitly set max_clients in its configuration.
  • Attack vector: Network-based, no authentication or valid HTTP request required — simply opening and holding open a large number of TCP connections to the httpd listener is sufficient.
  • Impact: High impact to availability only (no confidentiality or integrity impact); sustained connection flooding can exhaust worker processes, memory, and file descriptors, causing the server to become unresponsive or crash.

Affected software

  • Erlang/OTP: versions 17.0–27.3.4.16, 28.0–28.5.0.5, and 29.0–29.0.5
  • inets module (bundled with OTP): versions 5.10–9.3.2.6, 9.4–9.6.2.2, and 9.7–9.7.1
  • Only deployments of the inets httpd server that do not explicitly configure max_clients are vulnerable; servers with an explicit max_clients setting are not affected.

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • 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

Mitigation and recommended actions

  • Immediate: Upgrade to the patched Erlang/OTP releases: OTP 27.3.4.17, 28.5.0.6, or 29.0.6 (corresponding inets versions 9.3.2.7, 9.6.2.3, or 9.7.2, respectively).
  • If immediate patching is not possible:
    • Explicitly set {max_clients, 150} (or a value appropriate to your capacity) in the httpd server configuration to restore the intended connection-limiting safeguard.
    • Place a reverse proxy or load balancer in front of the httpd service and enforce concurrent-connection limits or rate limiting at that layer.
    • Restrict network access to the httpd listener to trusted clients/networks via firewall rules 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