Skip to content
Threat Brief

← All advisories

CVE-2026-66357

High 8.3No known exploitationFix available

inets,httpd:HTTP Request Smuggling via obs-fold Header Continuation

Record last updated

CVSS score

8.3

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.6%

Higher than 49% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

httpd has never implemented obs-fold (RFC 2616 §2.2 / RFC 7230 §3.2.4 header continuation lines). Every CRLF followed by a non-CRLF octet unconditionally starts a new header. This missing feature became a security concern as the understanding of HTTP request smuggling attacks evolved. This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, OTP 28.5.0.6, and OTP 29.0.6, corresponding to inets from 5.10 before 9.3.2.7, 9.6.2.3, and 9.7.2. Whether OTP before OTP 17.0, corresponding to inets before 5.10, is affected is unknown.

Weakness: CWE-444

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ErlangOTP17.0Not documentedCVE Program
ErlangOTP5.10Not documentedCVE Program
ErlangOTP84adefa331c4159d432d22840663c38f155cd4c1Not documentedCVE Program
Microsoftazl3 erlang 26.2.5.21-4 on Azure Linux 3.0Not documented26.2.5.21-6Microsoft MSRC
Microsoftazl3 erlang 26.2.5.21-6 on Azure Linux 3.0Not documented26.2.5.21-6Microsoft MSRC
ErlangOTP (unaffected)220d618d2479a7180b4a06d0c5aacfaa4af4a85bNot documentedCVE Program
ErlangOTP (unaffected)273d8958de38ff2a7fe0c5dcc5b6bfe6f65717f3Not documentedCVE Program
ErlangOTP (unaffected)e640d599287d2eba919e6f13b91f042d7dbe6ff4Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references