Skip to content
Web

CVE-2026-73812

8.3
High
EPSS 0.30%Patch availableSep 2, 2026

HTTP request-smuggling bug in Erlang/OTP inets causing front-end/back-end desync.

common questions

Is CVE-2026-73812 being exploited?

Not confirmed. CVE-2026-73812 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.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-73812?

CVE-2026-73812 is rated High with a CVSS score of 8.3. 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-73812?

Yes. A fix has been recorded for CVE-2026-73812. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73812 affect?

CVE-2026-73812 affects OTP from 17.0 before 27.3.4.17, OTP from 28.0 before 28.5.0.6, OTP from 29.0 before 29.0.6 (corresponding inets versions patched). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73812?

Upgrade to fixed OTP/inets releases; block or validate TE+CL at edge proxies/gateways.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OTP from 17.0 before 27.3.4.17OTP from 28.0 before 28.5.0.6OTP from 29.0 before 29.0.6 (corresponding inets versions patched)
impact

CL+TE request smuggling enables front-end/back-end desync: auth bypass, cache poisoning, request/response splitting, and data exposure.

action required

Immediate action required

affected versions
Erlang OTP
  • affected< 17.0
  • affected>= 17.0 and < 27.3.4.17
  • affected>= 28.0 and < 28.5.0.6
  • affected>= 29.0 and < 29.0.6
  • affected< 5.10
  • affected>= 5.10 and < 9.3.2.7
  • affected>= 9.4 and < 9.6.2.3
  • affected>= 9.7 and < 9.7.2
  • affected>= 84adefa331c4159d432d22840663c38f155cd4c1 and < 591dc00dc99dc2a426167a3b5257c0c94bd45e91

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free