Skip to content
Threat Brief

← All advisories

CVE-2026-73276

High 8.3No known exploitationFix available

inets, httpd: HTTP Request Smuggling via Whitespace-Before-Colon Header Dropping i

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 50% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Gracefulness code ignored cases that should be rejected, resulting in possible HTTP Request Smuggling opportunities. This issue affects OTP from OTP 22.2 before OTP 27.3.4.17, OTP 28.5.0.6, and OTP 29.0.6, corresponding to inets from 7.1.2 before 9.3.2.7, 9.6.2.3, and 9.7.2.

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
ErlangOTP22.2Not documentedCVE Program
ErlangOTP7.1.2Not documentedCVE Program
ErlangOTPc06db0bedf49a9b40725745e73fa82e562612815Not 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

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