CVE Tools

CVE-2026-73812

inets, httpd: HTTP Request Smuggling via Transfer-Encoding and Content-Length

No known exploitation. EPSS puts it in the 45th percentile. Fixed versions are out.

Check it yourself

OpenVAS · 3 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.190090

Run the check

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Erlang OTPAffected: ≥ 17.0, < 27.3.4.17Upgrade to: 27.3.4.17Affected: ≥ 28.0, < 28.5.0.6Upgrade to: 28.5.0.6Affected: ≥ 29.0, < 29.0.6Upgrade to: 29.0.6Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

httpd function check_header/3 rejects duplicate Content-Length (per CVE-2026-23941) but never checks for the TE+CL co-presence that RFC 9112 §6.3 identifies as a probable smuggling attempt. handle_body/3 frames by chunked and silently discards Content-Length. A CL-preferring front-end paired with chunked-preferring inets creates a classic CL.TE front-end/back-end desync. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to inets 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 before OTP 17.0, corresponding to inets before 5.10, is affected is unknown.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS45th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 45th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 7 days, from the signal feeds we watch.

  1. Record updated
  2. OpenVAS check added
  3. Publishedweakness classified, att&ck mapped, record updated, record updated, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for OTP, not every advisory.