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

Back
New CVE Detected

CVE-2026-69664 – Denial of Service (Worker Exhaustion) – Erlang/OTP inets httpd (OTP 18.1.4–29.0.5,

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-69664 is a denial-of-service vulnerability in the httpd HTTP server component of Erlang/OTP’s inets package, caused by improper handling of malformed chunked transfer-encoding requests. An unauthenticated remote attacker can exhaust all available server workers, denying service to legitimate clients. The vulnerability has a CVSS score of 8.7 (High).

Technical details

  • Root cause: when a chunked HTTP request’s chunk-size line arrives in a separate write from the headers, and that chunk-size line contains non-hexadecimal characters, the resulting error is converted into a return value instead of being handled properly, leaving the worker parked indefinitely.
  • Trigger condition: the request timeout for the connection has already been cancelled by the time the malformed chunk-size line arrives, and no byte-rate check reclaims the worker by default.
  • Attack vector: network, no authentication or user interaction required; the attacker sends a syntactically valid chunked request split across writes.
  • Impact: repeating the attack across multiple connections exhausts all available httpd workers, resulting in denial of service to legitimate clients.

Affected software

  • Erlang/OTP: 18.1.4 through 27.3.4.16
  • Erlang/OTP: 28.0 through 28.5.0.5
  • Erlang/OTP: 29.0 through 29.0.5
  • inets package: 6.0.3 through 9.3.2.6
  • inets package: 9.4 through 9.6.2.2
  • inets package: 9.7 through 9.7.1

Severity

CVSS 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 Erlang/OTP 27.3.4.17, 28.5.0.6, or 29.0.6 (inets 9.3.2.7, 9.6.2.3, or 9.7.2 respectively).
  • If patching is not immediately possible:
    • Configure the minimum_bytes_per_second httpd setting to enforce byte-rate checks on incoming connections.
    • Deploy a reverse proxy in front of httpd that validates and rejects malformed chunked transfer-encoding requests.
    • Restrict access to the httpd server to trusted clients where feasible.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge