← Back

CVE-2026-23941

nvd nist
Published: Mar 13, 2026Modified: Jul 24, 2026

JSON object

Loading...
7.0
Vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Show more
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XShow less
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db (Secondary)

Description

Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in Erlang OTP (inets httpd module) allows HTTP Request Smuggling. This vulnerability is associated with program files lib/inets/src/http_server/httpd_request.erl and program routines httpd_request:parse_headers/7. The server does not reject or normalize duplicate Content-Length headers. The earliest Content-Length in the request is used for body parsing while common reverse proxies (nginx, Apache httpd, Envoy) honor the last Content-Length value. This violates RFC 9112 Section 6.3 and allows front-end/back-end desynchronization, leaving attacker-controlled bytes queued as the start of the next request. This issue affects OTP from OTP 17.0 before OTP 28.4.1, OTP 27.3.4.9 and OTP 26.2.5.18, corresponding to inets from 5.10 before 9.6.1, 9.3.2.3 and 9.1.0.5.

Affected (6)

Erlang
2 products
Erlang/inets
Erlang/otp
Configuration A
6 vulnerable
Vulnerable SoftwareAffected Versions
Erlang
Erlang/inets
From 5.10 to 9.1.0.5
Erlang/inets
From 9.3 to 9.3.2.3
Erlang/inets
From 9.6 to 9.6.1
Erlang
Erlang/otp
From 17.0 to 26.2.5.18
Erlang/otp
From 27.0 to 27.3.4.9
Erlang/otp
From 28.0 to 28.4.1

Related CWEs

CWE-444
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

References (7)

Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Vendor Advisory
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Patch
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Patch
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Patch
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Vendor Advisory
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Third Party Advisory
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Product

Timeline

No history available yet.