CVE-2026-73812inets, httpd: HTTP Request Smuggling via Transfer-Encoding and Content-Length
Updated under an hour ago ()
Does this affect you?
It affects Erlang OTP. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 8.3 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
- Weakness (CWE)
- CWE-444
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- EEF
- NVD analysis
- Deferred
- Record last updated
- Sep 8, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Erlang OTP erlang:erlang/otp | before 17.0 status unknown; from 17.0 before 27.3.4.17; from 28.0 before 28.5.0.6; from 29.0 before 29.0.6 | CNA record |
References
- https://github.com/erlang/otp/security/advisories/GHSA-7j6m-4ffg-hg46vendor-advisory
- https://cna.erlef.org/cves/CVE-2026-73812.htmlrelated
- https://osv.dev/vulnerability/EEF-CVE-2026-73812related
- https://github.com/erlang/otp/commit/591dc00dc99dc2a426167a3b5257c0c94bd45e91patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.