CVE-2026-73276
HTTP request smuggling in Erlang/OTP inets allowing request parsing bypass.
Is CVE-2026-73276 being exploited?
Not confirmed. CVE-2026-73276 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-73276?
CVE-2026-73276 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73276?
Yes. A fix has been recorded for CVE-2026-73276. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73276 affect?
CVE-2026-73276 affects Erlang/OTP 22.2 < 27.3.4.17, Erlang/OTP 28.0 < 28.5.0.6, Erlang/OTP 29.0 < 29.0.6, inets 7.1.2 < 9.3.2.7, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73276?
Upgrade OTP/inets to fixed releases; test HTTP parsing and update WAF/cache rules.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Enables HTTP request smuggling—attackers can split/bypass requests, poison caches, evade WAFs, hijack sessions, or exfiltrate data.
Patch when possible
- affected>= 22.2 and < 27.3.4.17
- affected>= 28.0 and < 28.5.0.6
- affected>= 29.0 and < 29.0.6
- affected>= 7.1.2 and < 9.3.2.7
- affected>= 9.4 and < 9.6.2.3
- affected>= 9.7 and < 9.7.2
- affected>= c06db0bedf49a9b40725745e73fa82e562612815 and < *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.